Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de5264fde12357ad8bf1c8ecd9404a27731c91de0de2e62f1867f1f0cbe4a1a9

Tx prefix hash: edf6c253ab3ff5ac764bb286835ad18b8a99e2d196b97f322adff347f0ba3868
Tx public key: 1646075f6abe71d4057a885107c6091f3f7b1fb2a775f14191e1e4ae121f5998
Timestamp: 1708977490 Timestamp [UCT]: 2024-02-26 19:58:10 Age [y:d:h:m:s]: 01:049:15:11:28
Block: 966185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296486 RingCT/type: yes/0
Extra: 011646075f6abe71d4057a885107c6091f3f7b1fb2a775f14191e1e4ae121f599802110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbb8a1020181747ca90882418ad18f3c6740d43d9df32277689e39c9b3638c2d 0.600000000000 1425942 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": 966195, "vin": [ { "gen": { "height": 966185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbb8a1020181747ca90882418ad18f3c6740d43d9df32277689e39c9b3638c2d" } } ], "extra": [ 1, 22, 70, 7, 95, 106, 190, 113, 212, 5, 122, 136, 81, 7, 198, 9, 31, 63, 123, 31, 178, 167, 117, 241, 65, 145, 225, 228, 174, 18, 31, 89, 152, 2, 17, 0, 0, 0, 8, 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