Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8deb60cccec65ef310ab28b1f04b09c569002189b7857cc4bb5c992c573d88d1

Tx prefix hash: 394ec0b03764447a7e9bf1c441d109c7096c9a7203d67275f6735c3247dd5275
Tx public key: 7831f6501c021a5d8529941000a8f6f33ab75afea2eb36a0df7dc81f97852f51
Timestamp: 1705980317 Timestamp [UCT]: 2024-01-23 03:25:17 Age [y:d:h:m:s]: 01:288:02:30:22
Block: 941292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464720 RingCT/type: yes/0
Extra: 017831f6501c021a5d8529941000a8f6f33ab75afea2eb36a0df7dc81f97852f510211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b916bfc4806bb88c25a71dbcfddd6a4db7495ffa0eed284b6e66349d5bc7111f 0.600000000000 1399438 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": 941302, "vin": [ { "gen": { "height": 941292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b916bfc4806bb88c25a71dbcfddd6a4db7495ffa0eed284b6e66349d5bc7111f" } } ], "extra": [ 1, 120, 49, 246, 80, 28, 2, 26, 93, 133, 41, 148, 16, 0, 168, 246, 243, 58, 183, 90, 254, 162, 235, 54, 160, 223, 125, 200, 31, 151, 133, 47, 81, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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