Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c93c9f89a8eda0f4ce01d15282c5d0eb0f619d2731addc52bf634344f28599f

Tx prefix hash: c99129ec3ec9c68844fccfed90b56f68b91cd4aa3208da9bfa1b2ccf1c50562b
Tx public key: c48df3c412258ece6febdc6d825af8b7b3c9bf7429845552e414f4b7b3608543
Timestamp: 1710823174 Timestamp [UCT]: 2024-03-19 04:39:34 Age [y:d:h:m:s]: 01:020:04:51:19
Block: 981496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275388 RingCT/type: yes/0
Extra: 01c48df3c412258ece6febdc6d825af8b7b3c9bf7429845552e414f4b7b360854302110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a00e2e0eb2ca63d5cc004d5068189f450071b8107fab9c49e73732942555f25 0.600000000000 1441593 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": 981506, "vin": [ { "gen": { "height": 981496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a00e2e0eb2ca63d5cc004d5068189f450071b8107fab9c49e73732942555f25" } } ], "extra": [ 1, 196, 141, 243, 196, 18, 37, 142, 206, 111, 235, 220, 109, 130, 90, 248, 183, 179, 201, 191, 116, 41, 132, 85, 82, 228, 20, 244, 183, 179, 96, 133, 67, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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