Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a31a75dbea00f6c6bd2bc5910db20ceb715e9c41ad6f139f174860d0bfd7f0d

Tx prefix hash: 46fcba86d1b307146d2178786f6b3042290a5cf2aa57f2ddf4dc728ba627111d
Tx public key: 7113ba55973d1a6060f7c00bb06057a647fb26051a4199df34e7c5ae450f71af
Timestamp: 1713181965 Timestamp [UCT]: 2024-04-15 11:52:45 Age [y:d:h:m:s]: 00:268:10:18:00
Block: 1001024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192145 RingCT/type: yes/0
Extra: 017113ba55973d1a6060f7c00bb06057a647fb26051a4199df34e7c5ae450f71af02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 707d4ec5d59aa99720a5dc20d291835191c06b3a5062d7e89be7e508eb6eb610 0.600000000000 1461526 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": 1001034, "vin": [ { "gen": { "height": 1001024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "707d4ec5d59aa99720a5dc20d291835191c06b3a5062d7e89be7e508eb6eb610" } } ], "extra": [ 1, 113, 19, 186, 85, 151, 61, 26, 96, 96, 247, 192, 11, 176, 96, 87, 166, 71, 251, 38, 5, 26, 65, 153, 223, 52, 231, 197, 174, 69, 15, 113, 175, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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