Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ca54df39e66d9572cda0b45a027b92c6c2fb5f310d0e3e8111095e11ce0927

Tx prefix hash: da423a558da527e85df71ba9b0a16b820b40cd654cbc2d35f121f95d5bde57a3
Tx public key: 26e8de94d59236cb651c2bec3f31ede4dd1cc6c0ac1f7a99bfbe140446955547
Timestamp: 1702661038 Timestamp [UCT]: 2023-12-15 17:23:58 Age [y:d:h:m:s]: 01:328:21:22:24
Block: 913805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493912 RingCT/type: yes/0
Extra: 0126e8de94d59236cb651c2bec3f31ede4dd1cc6c0ac1f7a99bfbe14044695554702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4327245c0c35fcd7a26a564726dc3669a09fbfdeb0258069289979fef4b3692 0.600000000000 1371083 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": 913815, "vin": [ { "gen": { "height": 913805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4327245c0c35fcd7a26a564726dc3669a09fbfdeb0258069289979fef4b3692" } } ], "extra": [ 1, 38, 232, 222, 148, 213, 146, 54, 203, 101, 28, 43, 236, 63, 49, 237, 228, 221, 28, 198, 192, 172, 31, 122, 153, 191, 190, 20, 4, 70, 149, 85, 71, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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