Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24d8ae155572aeb67cfb9ced2dbbeff37ae760d11a3b4de6cba38b95b22f57f4

Tx prefix hash: a2c24fd0e8d4d5637de90403c34043b2e7493fdeb6d788c3e620e9cb00307767
Tx public key: bfb99917e81b12054883e56460b6b520ee26f8ad1e7aa1ba3e8d0ba436a57918
Timestamp: 1583632825 Timestamp [UCT]: 2020-03-08 02:00:25 Age [y:d:h:m:s]: 05:041:21:59:12
Block: 78306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185448 RingCT/type: yes/0
Extra: 01bfb99917e81b12054883e56460b6b520ee26f8ad1e7aa1ba3e8d0ba436a57918021100000003a33b4a85000000000000000000

1 output(s) for total of 337.707346238000 dcy

stealth address amount amount idx
00: 4f2c8e6c908afc6c45c5b1f215db2e0102b18cff22e18d75a845d12f6fae3d57 337.707346238000 143750 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": 78316, "vin": [ { "gen": { "height": 78306 } } ], "vout": [ { "amount": 337707346238, "target": { "key": "4f2c8e6c908afc6c45c5b1f215db2e0102b18cff22e18d75a845d12f6fae3d57" } } ], "extra": [ 1, 191, 185, 153, 23, 232, 27, 18, 5, 72, 131, 229, 100, 96, 182, 181, 32, 238, 38, 248, 173, 30, 122, 161, 186, 62, 141, 11, 164, 54, 165, 121, 24, 2, 17, 0, 0, 0, 3, 163, 59, 74, 133, 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