Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96d9c8f115b31a03c26f5297e975a963201acabe04ef9c9166d3392c109991fe

Tx prefix hash: 4d386d3fc2d2c7e7f98bf6c3e03bf91b83ebe43c4fe328e68c6e0b9f17ad0533
Tx public key: f91fef2b6c54ec7c4fcbd5530862b2b42d5b9bb54633e131f7242e32ff9153e9
Timestamp: 1736477908 Timestamp [UCT]: 2025-01-10 02:58:28 Age [y:d:h:m:s]: 00:070:14:51:12
Block: 1194024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50250 RingCT/type: yes/0
Extra: 01f91fef2b6c54ec7c4fcbd5530862b2b42d5b9bb54633e131f7242e32ff9153e9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29599f64052ac8df9783b8a55e91104480252c77dd7c5f07c5cf33a016e32fe3 0.600000000000 1680591 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": 1194034, "vin": [ { "gen": { "height": 1194024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29599f64052ac8df9783b8a55e91104480252c77dd7c5f07c5cf33a016e32fe3" } } ], "extra": [ 1, 249, 31, 239, 43, 108, 84, 236, 124, 79, 203, 213, 83, 8, 98, 178, 180, 45, 91, 155, 181, 70, 51, 225, 49, 247, 36, 46, 50, 255, 145, 83, 233, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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