Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ba70fc34853be4502bef52f5045bb4c9fbc0553dada7d2d69913afabdf722c

Tx prefix hash: 9ae49a768e6697b1eb66b9410fda57c9b14c691044da094e3025551cde3b594a
Tx public key: 456c8a4bcd9b3e27dc894137d49443c5d0731b8fd254274c927701d9891ce0a3
Timestamp: 1738646355 Timestamp [UCT]: 2025-02-04 05:19:15 Age [y:d:h:m:s]: 00:290:19:02:45
Block: 1211706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205599 RingCT/type: yes/0
Extra: 01456c8a4bcd9b3e27dc894137d49443c5d0731b8fd254274c927701d9891ce0a30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc357d72103b712221fc9d3936ef932da2e05c3d47ddae092a8b9fe3fb907da3 0.600000000000 1698469 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": 1211716, "vin": [ { "gen": { "height": 1211706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc357d72103b712221fc9d3936ef932da2e05c3d47ddae092a8b9fe3fb907da3" } } ], "extra": [ 1, 69, 108, 138, 75, 205, 155, 62, 39, 220, 137, 65, 55, 212, 148, 67, 197, 208, 115, 27, 143, 210, 84, 39, 76, 146, 119, 1, 217, 137, 28, 224, 163, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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