Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc202bce7a9758c597b3d2d65b28d014a80d2db93a82ad7916b25e8418a460c2

Tx prefix hash: 31afc0acddd6f8588ace90bc67c20443418d7011bf565df31780386f120bce08
Tx public key: f12b625380fd4498d9c8a8ba935537841b5a3928def8a36c1bd96e0bfaeff405
Timestamp: 1723491059 Timestamp [UCT]: 2024-08-12 19:30:59 Age [y:d:h:m:s]: 00:253:12:52:45
Block: 1086497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181094 RingCT/type: yes/0
Extra: 01f12b625380fd4498d9c8a8ba935537841b5a3928def8a36c1bd96e0bfaeff40502110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99b5a9ce6ccd5dc4733ee78077a382dc6e1f1401eca2cf30c539284dddcdf2e9 0.600000000000 1561094 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": 1086507, "vin": [ { "gen": { "height": 1086497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99b5a9ce6ccd5dc4733ee78077a382dc6e1f1401eca2cf30c539284dddcdf2e9" } } ], "extra": [ 1, 241, 43, 98, 83, 128, 253, 68, 152, 217, 200, 168, 186, 147, 85, 55, 132, 27, 90, 57, 40, 222, 248, 163, 108, 27, 217, 110, 11, 250, 239, 244, 5, 2, 17, 0, 0, 0, 10, 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