Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0120a669c40b9edf86d7ff1851f7acbf7d6bfb32bf6bdf9306c31e310c47f278

Tx prefix hash: 476d16e227b42cc2bfc0eade55fc3d9ddb3b5eac3a35065cac41e0d2d21704fa
Tx public key: 294aee2f442735635900b90b918a389407849e30e587606db576d5a518f460b6
Timestamp: 1704595476 Timestamp [UCT]: 2024-01-07 02:44:36 Age [y:d:h:m:s]: 01:017:22:40:19
Block: 929819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274135 RingCT/type: yes/0
Extra: 01294aee2f442735635900b90b918a389407849e30e587606db576d5a518f460b602110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e0ce9a01eb84fe649a523a91edb6cd2f10e0bfc5aedb8bbcb0a9cf326b1dae1 0.600000000000 1387695 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": 929829, "vin": [ { "gen": { "height": 929819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e0ce9a01eb84fe649a523a91edb6cd2f10e0bfc5aedb8bbcb0a9cf326b1dae1" } } ], "extra": [ 1, 41, 74, 238, 47, 68, 39, 53, 99, 89, 0, 185, 11, 145, 138, 56, 148, 7, 132, 158, 48, 229, 135, 96, 109, 181, 118, 213, 165, 24, 244, 96, 182, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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