Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e482c4ef81002cc8df3bd770459de667a60b09befc26ef4618a5d250c037150e

Tx prefix hash: 1e8476f6c46adc9a2753f229874013a8bf068181e5ee1e3bd22a1ee36f5dd779
Tx public key: f24abe8f6a712b984ee9181339e095675d007c5c2d1f9e3fdfd03512b5370f16
Timestamp: 1751315226 Timestamp [UCT]: 2025-06-30 20:27:06 Age [y:d:h:m:s]: 00:142:11:51:57
Block: 1316081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100032 RingCT/type: yes/0
Extra: 01f24abe8f6a712b984ee9181339e095675d007c5c2d1f9e3fdfd03512b5370f1602110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b83c0f690e96fc66037ee940f34cf5f6ed42c7db7c363e4ee45950eb3d7111c 0.600000000000 1803738 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": 1316091, "vin": [ { "gen": { "height": 1316081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b83c0f690e96fc66037ee940f34cf5f6ed42c7db7c363e4ee45950eb3d7111c" } } ], "extra": [ 1, 242, 74, 190, 143, 106, 113, 43, 152, 78, 233, 24, 19, 57, 224, 149, 103, 93, 0, 124, 92, 45, 31, 158, 63, 223, 208, 53, 18, 181, 55, 15, 22, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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