Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d888fad9279eb311670f7d80b5f74914d5447f9e5848f89a82e8ad9496e4da98

Tx prefix hash: a575d15264f272b57338697c4fb7264a8900b607b5666a730743280ea6697df0
Tx public key: cfb92bd1b6f54b8086babc55ebd10e9b1efc6a1709d35109ae75daf69d8fbc4e
Timestamp: 1705103016 Timestamp [UCT]: 2024-01-12 23:43:36 Age [y:d:h:m:s]: 01:065:08:02:10
Block: 934035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307795 RingCT/type: yes/0
Extra: 01cfb92bd1b6f54b8086babc55ebd10e9b1efc6a1709d35109ae75daf69d8fbc4e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8510e009a5cec8517f35400e159c3f61b739a3a97a23d15fd65e4a4cf34586ea 0.600000000000 1392021 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": 934045, "vin": [ { "gen": { "height": 934035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8510e009a5cec8517f35400e159c3f61b739a3a97a23d15fd65e4a4cf34586ea" } } ], "extra": [ 1, 207, 185, 43, 209, 182, 245, 75, 128, 134, 186, 188, 85, 235, 209, 14, 155, 30, 252, 106, 23, 9, 211, 81, 9, 174, 117, 218, 246, 157, 143, 188, 78, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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