Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39aeebb6f1aabb1d8560e057f54cd4447b9887f0e358255207a5028ff3e87a8b

Tx prefix hash: 8dfe28c0d02e08a126f36ab18e663388347d563769a8a61482d2e23bb1a23137
Tx public key: fed97226c908bfd6b2c47a4384ec41170291d288bb7c3ae48ebb7813dc2e68c7
Timestamp: 1711740386 Timestamp [UCT]: 2024-03-29 19:26:26 Age [y:d:h:m:s]: 01:019:10:37:46
Block: 989103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274849 RingCT/type: yes/0
Extra: 01fed97226c908bfd6b2c47a4384ec41170291d288bb7c3ae48ebb7813dc2e68c702110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 794a5a2f999949097d253362c5cf57e891bf9e6cf163e8b58512ec7aa0be9200 0.600000000000 1449398 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": 989113, "vin": [ { "gen": { "height": 989103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "794a5a2f999949097d253362c5cf57e891bf9e6cf163e8b58512ec7aa0be9200" } } ], "extra": [ 1, 254, 217, 114, 38, 201, 8, 191, 214, 178, 196, 122, 67, 132, 236, 65, 23, 2, 145, 210, 136, 187, 124, 58, 228, 142, 187, 120, 19, 220, 46, 104, 199, 2, 17, 0, 0, 0, 9, 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