Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9752963c6ec3a1161ba03946e67bdc2d132f98b8850498f49aa223e1889b1bb3

Tx prefix hash: 80e5d44aadb5c2b7aa91ae37594e7007599f5ed176f0b6cc862b29801c0af831
Tx public key: d851d481bc982faf1c1d2d7a9d2c3cfe2340ed19b8e38c56d9be320dc53a3d57
Timestamp: 1741396686 Timestamp [UCT]: 2025-03-08 01:18:06 Age [y:d:h:m:s]: 00:258:13:45:20
Block: 1234485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182535 RingCT/type: yes/0
Extra: 01d851d481bc982faf1c1d2d7a9d2c3cfe2340ed19b8e38c56d9be320dc53a3d57021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c80631f43fd91e8e2f6f257923479da64b368ebe65e3028f3426d7f7035f7c90 0.600000000000 1721412 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": 1234495, "vin": [ { "gen": { "height": 1234485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c80631f43fd91e8e2f6f257923479da64b368ebe65e3028f3426d7f7035f7c90" } } ], "extra": [ 1, 216, 81, 212, 129, 188, 152, 47, 175, 28, 29, 45, 122, 157, 44, 60, 254, 35, 64, 237, 25, 184, 227, 140, 86, 217, 190, 50, 13, 197, 58, 61, 87, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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