Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dec562a0ad95d0332a5e9fc39a45bf31d74f498a72f9f3db0a2f70156fa0139

Tx prefix hash: 858e47cdddbf99d87f446a4195bf5d5ec845eb56900a7d1a0c302bcb247c4374
Tx public key: acfa3205d947d15624df37ad067ab581a217e7ae1311f91bcf79e39f9cfbc5e6
Timestamp: 1703481307 Timestamp [UCT]: 2023-12-25 05:15:07 Age [y:d:h:m:s]: 01:319:11:06:55
Block: 920614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487150 RingCT/type: yes/0
Extra: 01acfa3205d947d15624df37ad067ab581a217e7ae1311f91bcf79e39f9cfbc5e602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2910bd89eddef8f8df42ada2c37aa2fdaf61571cf4165b8c111e74fe573d2a1b 0.600000000000 1378294 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": 920624, "vin": [ { "gen": { "height": 920614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2910bd89eddef8f8df42ada2c37aa2fdaf61571cf4165b8c111e74fe573d2a1b" } } ], "extra": [ 1, 172, 250, 50, 5, 217, 71, 209, 86, 36, 223, 55, 173, 6, 122, 181, 129, 162, 23, 231, 174, 19, 17, 249, 27, 207, 121, 227, 159, 156, 251, 197, 230, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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