Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c21ed24ea74edc70930e1fe69e9c0a781c7eedc6083da00e6e1196deb954498a

Tx prefix hash: 23f79dceea534106afc4488dbb09fff3e1b19b408be4429a76c50dd9535d7d7e
Tx public key: 167f8419b06669dc7f4645943c66e544debb8d4b7184d688acb9ed1846a96a98
Timestamp: 1592761054 Timestamp [UCT]: 2020-06-21 17:37:34 Age [y:d:h:m:s]: 04:190:08:47:00
Block: 110141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074564 RingCT/type: yes/0
Extra: 01167f8419b06669dc7f4645943c66e544debb8d4b7184d688acb9ed1846a96a9802110000002546a11e8a000000000000000000

1 output(s) for total of 264.885321743000 dcy

stealth address amount amount idx
00: ad8bc075f967cf591a7b7d576c2c45e001f17d5816812fe8499430a1c20e4d8b 264.885321743000 190771 of 0

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": 110151, "vin": [ { "gen": { "height": 110141 } } ], "vout": [ { "amount": 264885321743, "target": { "key": "ad8bc075f967cf591a7b7d576c2c45e001f17d5816812fe8499430a1c20e4d8b" } } ], "extra": [ 1, 22, 127, 132, 25, 176, 102, 105, 220, 127, 70, 69, 148, 60, 102, 229, 68, 222, 187, 141, 75, 113, 132, 214, 136, 172, 185, 237, 24, 70, 169, 106, 152, 2, 17, 0, 0, 0, 37, 70, 161, 30, 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