Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c0af1e14ab45b53a9984378f56c42b0c419a816e3b7385e814f3f2b019f4f03

Tx prefix hash: 7132d279400dd51970f964aec437548e7107a6c8a69755b8c2b7694c3474c0b3
Tx public key: 8219915948bbc63b74a2a9c3e635095d08b46039e6377e45b3e535fecce4ffab
Timestamp: 1705379660 Timestamp [UCT]: 2024-01-16 04:34:20 Age [y:d:h:m:s]: 01:303:09:15:18
Block: 936321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475664 RingCT/type: yes/0
Extra: 018219915948bbc63b74a2a9c3e635095d08b46039e6377e45b3e535fecce4ffab0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5be0319fe30ff41e69ad87a8c19c4a72dc528a70abc1006693fccb3c2e7671 0.600000000000 1394345 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": 936331, "vin": [ { "gen": { "height": 936321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5be0319fe30ff41e69ad87a8c19c4a72dc528a70abc1006693fccb3c2e7671" } } ], "extra": [ 1, 130, 25, 145, 89, 72, 187, 198, 59, 116, 162, 169, 195, 230, 53, 9, 93, 8, 180, 96, 57, 230, 55, 126, 69, 179, 229, 53, 254, 204, 228, 255, 171, 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