Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1b35a3f9150864abc26f6158ee17e058bcb22db72df9ab56ecff7d968f1bd97

Tx prefix hash: 2d98689b28793557aaa2ce6c402efc0c158f90c57e62400725865e6247212f8d
Tx public key: d663ff30002420b4a56e434e5a9cd444831c37055c1b3d2760b3c96cabab2cfb
Timestamp: 1760669970 Timestamp [UCT]: 2025-10-17 02:59:30 Age [y:d:h:m:s]: 00:102:19:32:59
Block: 1391616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73430 RingCT/type: yes/0
Extra: 01d663ff30002420b4a56e434e5a9cd444831c37055c1b3d2760b3c96cabab2cfb0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c9ce7f8adbd8a52f835c8d4cf9a7fd0c21b364efe25fbeb8e7da1a0ff38e7af 0.600000000000 1879863 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": 1391626, "vin": [ { "gen": { "height": 1391616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c9ce7f8adbd8a52f835c8d4cf9a7fd0c21b364efe25fbeb8e7da1a0ff38e7af" } } ], "extra": [ 1, 214, 99, 255, 48, 0, 36, 32, 180, 165, 110, 67, 78, 90, 156, 212, 68, 131, 28, 55, 5, 92, 27, 61, 39, 96, 179, 201, 108, 171, 171, 44, 251, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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