Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 359d8133a9e743d8859d4883c7242b6388c443b74284f690ea48f83b109fb613

Tx prefix hash: 85dc53cb3510f27ff9ead65ae0e3ecb5f42ee2c65bccb97ed25d1f9648b3c5cb
Tx public key: 9721835e4c650ba297281cc5bc7c03cad0537fa0c4ef8235cadb6e7073ff9de8
Timestamp: 1745614706 Timestamp [UCT]: 2025-04-25 20:58:26 Age [y:d:h:m:s]: 00:257:11:02:07
Block: 1269399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181797 RingCT/type: yes/0
Extra: 019721835e4c650ba297281cc5bc7c03cad0537fa0c4ef8235cadb6e7073ff9de8021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e09732aa442552e3593bc5cc8ea6b8ada1bcd3d98ee04d7597fdc43ae7bc47d 0.600000000000 1756634 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": 1269409, "vin": [ { "gen": { "height": 1269399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e09732aa442552e3593bc5cc8ea6b8ada1bcd3d98ee04d7597fdc43ae7bc47d" } } ], "extra": [ 1, 151, 33, 131, 94, 76, 101, 11, 162, 151, 40, 28, 197, 188, 124, 3, 202, 208, 83, 127, 160, 196, 239, 130, 53, 202, 219, 110, 112, 115, 255, 157, 232, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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