Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4674b2300b4333f4df49ef1c9969141364dfe7decb004aa54f8d41adfaa9bdf1

Tx prefix hash: 80e9f85905563c03f561ce543ae29c061046d9c0e773a672cf8a6e0e079f11fa
Tx public key: f60f6e040738f81e07e1e189de13cfe4f9cfe2dfac4128bec16b8dc46e69e04f
Timestamp: 1709221015 Timestamp [UCT]: 2024-02-29 15:36:55 Age [y:d:h:m:s]: 01:014:09:18:44
Block: 968199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271299 RingCT/type: yes/0
Extra: 01f60f6e040738f81e07e1e189de13cfe4f9cfe2dfac4128bec16b8dc46e69e04f0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7065a82754a16e1382c6cfc258e29d799af8708a1bc0b9fb161d615c2882e45b 0.600000000000 1428000 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": 968209, "vin": [ { "gen": { "height": 968199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7065a82754a16e1382c6cfc258e29d799af8708a1bc0b9fb161d615c2882e45b" } } ], "extra": [ 1, 246, 15, 110, 4, 7, 56, 248, 30, 7, 225, 225, 137, 222, 19, 207, 228, 249, 207, 226, 223, 172, 65, 40, 190, 193, 107, 141, 196, 110, 105, 224, 79, 2, 17, 0, 0, 0, 7, 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