Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d35195f71285844223d0af57a4b96f4446cd5c4821baaccfaffd826d0d8a47

Tx prefix hash: ab9f6f74b828a15ddf793080eac5d05f3bfe48ca023c1b232e5667a499650376
Tx public key: 9e1b2c24501b0fd5c89476e8fe8c4bd3539dd48e2e7377392d342a97982a070d
Timestamp: 1743801267 Timestamp [UCT]: 2025-04-04 21:14:27 Age [y:d:h:m:s]: 00:218:19:19:30
Block: 1254381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154111 RingCT/type: yes/0
Extra: 019e1b2c24501b0fd5c89476e8fe8c4bd3539dd48e2e7377392d342a97982a070d0211000000074060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 074300ceb8a2a548e8013588444d62ad64d58a9a8e66a921b9cdf61e80b4bdf8 0.600000000000 1741462 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": 1254391, "vin": [ { "gen": { "height": 1254381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "074300ceb8a2a548e8013588444d62ad64d58a9a8e66a921b9cdf61e80b4bdf8" } } ], "extra": [ 1, 158, 27, 44, 36, 80, 27, 15, 213, 200, 148, 118, 232, 254, 140, 75, 211, 83, 157, 212, 142, 46, 115, 119, 57, 45, 52, 42, 151, 152, 42, 7, 13, 2, 17, 0, 0, 0, 7, 64, 96, 246, 210, 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