Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2a3a05fc952990759ee01e0a47e22ed82b3a4b144dcaa24752899b9c748c577

Tx prefix hash: 9803685c0305f0506c295dabe5560629c8c84f0a05b32dfc8c3f81fd9c3a7aa2
Tx public key: cc957d4065f3d50a4a859bf3ceaf9972ffe3a98532e06cafc64516ed966e05ca
Timestamp: 1706110456 Timestamp [UCT]: 2024-01-24 15:34:16 Age [y:d:h:m:s]: 01:105:09:31:09
Block: 942374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336435 RingCT/type: yes/0
Extra: 01cc957d4065f3d50a4a859bf3ceaf9972ffe3a98532e06cafc64516ed966e05ca0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9d3dbb7f9cfae6c3ff63a89d288bfd3ebf3f8423f89d9d6f2988dce9d6cc476 0.600000000000 1400544 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": 942384, "vin": [ { "gen": { "height": 942374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9d3dbb7f9cfae6c3ff63a89d288bfd3ebf3f8423f89d9d6f2988dce9d6cc476" } } ], "extra": [ 1, 204, 149, 125, 64, 101, 243, 213, 10, 74, 133, 155, 243, 206, 175, 153, 114, 255, 227, 169, 133, 50, 224, 108, 175, 198, 69, 22, 237, 150, 110, 5, 202, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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