Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f42d6f08b2d3ead3314636a3785539c051c159283c61860c0220373dc6b690c

Tx prefix hash: 6a8d0792400a21f4b131c9a4a6e688e72aa22debcd07a421d709b9b0c1b3896e
Tx public key: 88ee3d07ff1a8514d09f2f666eb2ab2009c038211d80e8b4262034914da9f698
Timestamp: 1723477137 Timestamp [UCT]: 2024-08-12 15:38:57 Age [y:d:h:m:s]: 01:093:17:11:33
Block: 1086382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325455 RingCT/type: yes/0
Extra: 0188ee3d07ff1a8514d09f2f666eb2ab2009c038211d80e8b4262034914da9f698021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bda0d0e26664e4d791cd83f2fe7f59efbddcd555f3f1881fd9f443c215d8a9d 0.600000000000 1560979 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": 1086392, "vin": [ { "gen": { "height": 1086382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bda0d0e26664e4d791cd83f2fe7f59efbddcd555f3f1881fd9f443c215d8a9d" } } ], "extra": [ 1, 136, 238, 61, 7, 255, 26, 133, 20, 208, 159, 47, 102, 110, 178, 171, 32, 9, 192, 56, 33, 29, 128, 232, 180, 38, 32, 52, 145, 77, 169, 246, 152, 2, 17, 0, 0, 0, 4, 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