Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c2be215a9cdbb4575398eebf24aa36b82a8a9efdf534fb4b196880b88ddf801c

Tx prefix hash: 78438def89ac0bb86c63e4b889329f8ab2bdbb388e8e27ec11ed9eb1277f44d1
Tx public key: 31fff5b9f6784ffa2e304fcba60d3c0afb737b62efe7e9294156a4cccfddde7b
Timestamp: 1706282724 Timestamp [UCT]: 2024-01-26 15:25:24 Age [y:d:h:m:s]: 01:145:22:30:20
Block: 943804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365289 RingCT/type: yes/0
Extra: 0131fff5b9f6784ffa2e304fcba60d3c0afb737b62efe7e9294156a4cccfddde7b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1e3a1f1852b63d290af54f13afbf184fd3e7c4d1174c48f7c1b16377bc5784e 0.600000000000 1402030 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 943814, "vin": [ { "gen": { "height": 943804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1e3a1f1852b63d290af54f13afbf184fd3e7c4d1174c48f7c1b16377bc5784e" } } ], "extra": [ 1, 49, 255, 245, 185, 246, 120, 79, 250, 46, 48, 79, 203, 166, 13, 60, 10, 251, 115, 123, 98, 239, 231, 233, 41, 65, 86, 164, 204, 207, 221, 222, 123, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8