Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a29aa11464397d6d41e1d75f328fca2db5157e0d876b596436e045b208760f34

Tx prefix hash: 5061b00e8f4ba6e01cbd5a10c0ac64274af0c91eff83db3a89c768e66a76af82
Tx public key: c358bfc7bc257ac1fa984cb6f76c3dd15c56147952e053f3c3fa3d64e52bf4b6
Timestamp: 1705712837 Timestamp [UCT]: 2024-01-20 01:07:17 Age [y:d:h:m:s]: 01:146:09:38:01
Block: 939070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365719 RingCT/type: yes/0
Extra: 01c358bfc7bc257ac1fa984cb6f76c3dd15c56147952e053f3c3fa3d64e52bf4b602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dee1aaf0d6408f61ee2b85617bea6331bf063b518807025f79144927043d3211 0.600000000000 1397154 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": 939080, "vin": [ { "gen": { "height": 939070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dee1aaf0d6408f61ee2b85617bea6331bf063b518807025f79144927043d3211" } } ], "extra": [ 1, 195, 88, 191, 199, 188, 37, 122, 193, 250, 152, 76, 182, 247, 108, 61, 209, 92, 86, 20, 121, 82, 224, 83, 243, 195, 250, 61, 100, 229, 43, 244, 182, 2, 17, 0, 0, 0, 3, 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