Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e3b467483fe07c925813300a77a37a2733b0a4c344d88cd950253d344c1426c

Tx prefix hash: 792e1ded33e355c22c7baebdbef5e8575f77e6825e5ba7231841016ff3cf4930
Tx public key: da2643edc51c24c8b5cd1f2af7edf8b855703aefa34ed2fb216fc08f1f223b06
Timestamp: 1737433322 Timestamp [UCT]: 2025-01-21 04:22:02 Age [y:d:h:m:s]: 00:148:08:09:10
Block: 1201888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105769 RingCT/type: yes/0
Extra: 01da2643edc51c24c8b5cd1f2af7edf8b855703aefa34ed2fb216fc08f1f223b06021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d742117292b525ae4d960e22d81625825d7d1fd1937d99abdf131c95664e4e59 0.600000000000 1688545 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": 1201898, "vin": [ { "gen": { "height": 1201888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d742117292b525ae4d960e22d81625825d7d1fd1937d99abdf131c95664e4e59" } } ], "extra": [ 1, 218, 38, 67, 237, 197, 28, 36, 200, 181, 205, 31, 42, 247, 237, 248, 184, 85, 112, 58, 239, 163, 78, 210, 251, 33, 111, 192, 143, 31, 34, 59, 6, 2, 17, 0, 0, 0, 1, 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