Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5611a5fa935251a73c1eb0213f48f805ae3c1d9279c18c08d77b37f9f3d3f471

Tx prefix hash: 40fa1b6bda1ee72ad7c3550dd9871d8be42d2eaad22faa9261239ec04f9f07fd
Tx public key: fa8e1902414913441c9aa9b4b1d9b7a2af3bb02d987a3bdc6f3379de86ce8293
Timestamp: 1726001937 Timestamp [UCT]: 2024-09-10 20:58:57 Age [y:d:h:m:s]: 00:226:20:26:02
Block: 1107313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161980 RingCT/type: yes/0
Extra: 01fa8e1902414913441c9aa9b4b1d9b7a2af3bb02d987a3bdc6f3379de86ce8293021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 117bb3eb3c6e607b35046be356e3817ccfa8aba2c5ad87dc043f332a03f0fc87 0.600000000000 1584924 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": 1107323, "vin": [ { "gen": { "height": 1107313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "117bb3eb3c6e607b35046be356e3817ccfa8aba2c5ad87dc043f332a03f0fc87" } } ], "extra": [ 1, 250, 142, 25, 2, 65, 73, 19, 68, 28, 154, 169, 180, 177, 217, 183, 162, 175, 59, 176, 45, 152, 122, 59, 220, 111, 51, 121, 222, 134, 206, 130, 147, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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