Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82887ec05dbde277c1e35b379887dced1894ace2d6404d92dcb463f0dae7fc10

Tx prefix hash: 3de9d493a561cb4f8e12032ebdea1e28d1a746121c5b4deea14586001a36b050
Tx public key: 3f4a80de58419e1af2d26c654ca0a1d1fd32fbe835b705d12c4c3505bd54d777
Timestamp: 1716237052 Timestamp [UCT]: 2024-05-20 20:30:52 Age [y:d:h:m:s]: 00:343:04:50:12
Block: 1026368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245315 RingCT/type: yes/0
Extra: 013f4a80de58419e1af2d26c654ca0a1d1fd32fbe835b705d12c4c3505bd54d777021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d15432e5095bdc1f5ea575dd47c60b29338bed91c82c717424abde36295f277d 0.600000000000 1493411 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": 1026378, "vin": [ { "gen": { "height": 1026368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d15432e5095bdc1f5ea575dd47c60b29338bed91c82c717424abde36295f277d" } } ], "extra": [ 1, 63, 74, 128, 222, 88, 65, 158, 26, 242, 210, 108, 101, 76, 160, 161, 209, 253, 50, 251, 232, 53, 183, 5, 209, 44, 76, 53, 5, 189, 84, 215, 119, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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