Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d620f741c80f63902534e2646c2457e33900353c6bffa084181caa1097fd0c05

Tx prefix hash: cc5aeec1b389a8f8ea2837a525db153ec9d09ebffc86d526501b7058d8fcfdf2
Tx public key: 39d040aef82847e2b1de3badefef6f6f4ee6d9681a002956aaefbd0df26fc464
Timestamp: 1763486843 Timestamp [UCT]: 2025-11-18 17:27:23 Age [y:d:h:m:s]: 00:009:12:25:32
Block: 1414959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6813 RingCT/type: yes/0
Extra: 0139d040aef82847e2b1de3badefef6f6f4ee6d9681a002956aaefbd0df26fc46402110000000343b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e09e408e294cb095d224aef6e2c423c4229618b7643e326cf6f7ca2b1ceaeaf 0.600000000000 1903452 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": 1414969, "vin": [ { "gen": { "height": 1414959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e09e408e294cb095d224aef6e2c423c4229618b7643e326cf6f7ca2b1ceaeaf" } } ], "extra": [ 1, 57, 208, 64, 174, 248, 40, 71, 226, 177, 222, 59, 173, 239, 239, 111, 111, 78, 230, 217, 104, 26, 0, 41, 86, 170, 239, 189, 13, 242, 111, 196, 100, 2, 17, 0, 0, 0, 3, 67, 181, 4, 113, 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