Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd331b65eda9515c66639b00650aa444d3a559799b81bd3403db85f6a1b44f34

Tx prefix hash: 57117270e262b67e0840243e482075d7dc9ec247c1585d5a72e7b7f19c609a3b
Tx public key: 067caaf88ad9d764e720f46df84aeaf50a6ac6fee37fdd23b13521f2d0966248
Timestamp: 1757158572 Timestamp [UCT]: 2025-09-06 11:36:12 Age [y:d:h:m:s]: 00:090:10:52:05
Block: 1362592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64680 RingCT/type: yes/0
Extra: 01067caaf88ad9d764e720f46df84aeaf50a6ac6fee37fdd23b13521f2d096624802110000001ab2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fe9e1b0d8a4e596ee7d8e45d4ebf57d0acfecabd57d43c6f7edf351f945d76c 0.600000000000 1850623 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": 1362602, "vin": [ { "gen": { "height": 1362592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fe9e1b0d8a4e596ee7d8e45d4ebf57d0acfecabd57d43c6f7edf351f945d76c" } } ], "extra": [ 1, 6, 124, 170, 248, 138, 217, 215, 100, 231, 32, 244, 109, 248, 74, 234, 245, 10, 106, 198, 254, 227, 127, 221, 35, 177, 53, 33, 242, 208, 150, 98, 72, 2, 17, 0, 0, 0, 26, 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