Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5e7af792a3f369c64d3c679ff54d41fc3f2c149a009147533926d516f184e02

Tx prefix hash: dfb06044cd14884636d08397ab00d6777ed57e18ef6c2e7f1ff5187268d6b671
Tx public key: 8fb8a1a0d8f64d39d441b81ef826d9750dfeb4329f1a034e6b2e2674dbde5908
Timestamp: 1735047357 Timestamp [UCT]: 2024-12-24 13:35:57 Age [y:d:h:m:s]: 00:123:21:54:37
Block: 1182188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88367 RingCT/type: yes/0
Extra: 018fb8a1a0d8f64d39d441b81ef826d9750dfeb4329f1a034e6b2e2674dbde5908021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ee55785670247565c44cb83c280a91337434296e461315e10d487c8a6f31d3c 0.600000000000 1668621 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": 1182198, "vin": [ { "gen": { "height": 1182188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ee55785670247565c44cb83c280a91337434296e461315e10d487c8a6f31d3c" } } ], "extra": [ 1, 143, 184, 161, 160, 216, 246, 77, 57, 212, 65, 184, 30, 248, 38, 217, 117, 13, 254, 180, 50, 159, 26, 3, 78, 107, 46, 38, 116, 219, 222, 89, 8, 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