Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72921c64dda2e30d6f38fd61f4d833a38e398e17a8ee1ef91174a2edfa018f6e

Tx prefix hash: 0341cb6eaf2651348756f15505ff2f83db0ebce1e33e1eb1ec7c98966c3f7108
Tx public key: adea6cfed4513468b30e4ddba530e029d58be5ad031af9fa6f9cab4535e2abef
Timestamp: 1752203874 Timestamp [UCT]: 2025-07-11 03:17:54 Age [y:d:h:m:s]: 00:180:06:14:44
Block: 1323020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127506 RingCT/type: yes/0
Extra: 01adea6cfed4513468b30e4ddba530e029d58be5ad031af9fa6f9cab4535e2abef021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 684cbf372d63170ae0f0ed7a8dd14e953ce79398c4d8da8ea9fc3b2c0138b331 0.600000000000 1810753 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": 1323030, "vin": [ { "gen": { "height": 1323020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "684cbf372d63170ae0f0ed7a8dd14e953ce79398c4d8da8ea9fc3b2c0138b331" } } ], "extra": [ 1, 173, 234, 108, 254, 212, 81, 52, 104, 179, 14, 77, 219, 165, 48, 224, 41, 213, 139, 229, 173, 3, 26, 249, 250, 111, 156, 171, 69, 53, 226, 171, 239, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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