Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 507b2d8d39d7fca5d8ea9e4b0c63e95754b6c183c8860ac5eeaa094f1f044869

Tx prefix hash: 4677825cf84011780127f4bad9844ac1dd309125f5d19032f0215612e4571401
Tx public key: c8156207e36e9923053c60840eac42a5f8dc63cdae24744a9ffac3b2329bc627
Timestamp: 1705289861 Timestamp [UCT]: 2024-01-15 03:37:41 Age [y:d:h:m:s]: 01:121:13:09:47
Block: 935573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348003 RingCT/type: yes/0
Extra: 01c8156207e36e9923053c60840eac42a5f8dc63cdae24744a9ffac3b2329bc62702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3333e109e57ebd74c1d3a4c7f501b9d9b66584225c7121c5e0da5d5f0c087cee 0.600000000000 1393589 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": 935583, "vin": [ { "gen": { "height": 935573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3333e109e57ebd74c1d3a4c7f501b9d9b66584225c7121c5e0da5d5f0c087cee" } } ], "extra": [ 1, 200, 21, 98, 7, 227, 110, 153, 35, 5, 60, 96, 132, 14, 172, 66, 165, 248, 220, 99, 205, 174, 36, 116, 74, 159, 250, 195, 178, 50, 155, 198, 39, 2, 17, 0, 0, 0, 3, 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