Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbb5594d11d2dd4bef771e8595f83bb7cdb3831b7e838454e5b350caa00e039e

Tx prefix hash: 3a35c70907d1faf39be67f701fab24f78752d34b65b449ceeceb40ab20f7219a
Tx public key: 9b1895cc501e6e99a905b5ee53e5ee6bc02c23cdd3ba4105097c762acf24a61f
Timestamp: 1757392094 Timestamp [UCT]: 2025-09-09 04:28:14 Age [y:d:h:m:s]: 00:121:02:24:54
Block: 1364539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86626 RingCT/type: yes/0
Extra: 019b1895cc501e6e99a905b5ee53e5ee6bc02c23cdd3ba4105097c762acf24a61f02110000000bb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e5a1ef4a9935a53dcf68e2c3c1526f48c06b29ed924c99e21eda1dc6fc1e06f 0.600000000000 1852578 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": 1364549, "vin": [ { "gen": { "height": 1364539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e5a1ef4a9935a53dcf68e2c3c1526f48c06b29ed924c99e21eda1dc6fc1e06f" } } ], "extra": [ 1, 155, 24, 149, 204, 80, 30, 110, 153, 169, 5, 181, 238, 83, 229, 238, 107, 192, 44, 35, 205, 211, 186, 65, 5, 9, 124, 118, 42, 207, 36, 166, 31, 2, 17, 0, 0, 0, 11, 178, 247, 132, 196, 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