Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7daf4f5c67e830722a1c8894a604bcfb452bb25570f0f8348abf9399b52b39

Tx prefix hash: 8b6cee2993377f9370ee96dedcbfbfd379cef919da63efe01b65b54ed95b56b2
Tx public key: e0225c8394a2d5d782dd6fec2fb2cadf8195efd2acbdd0a4dea8eac777554fb5
Timestamp: 1733614860 Timestamp [UCT]: 2024-12-07 23:41:00 Age [y:d:h:m:s]: 00:122:12:02:35
Block: 1170332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87351 RingCT/type: yes/0
Extra: 01e0225c8394a2d5d782dd6fec2fb2cadf8195efd2acbdd0a4dea8eac777554fb5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0554622e25703c6f42255f639eade9705cc7ac6e637a2d479f3c793ec1c0181 0.600000000000 1656061 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": 1170342, "vin": [ { "gen": { "height": 1170332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0554622e25703c6f42255f639eade9705cc7ac6e637a2d479f3c793ec1c0181" } } ], "extra": [ 1, 224, 34, 92, 131, 148, 162, 213, 215, 130, 221, 111, 236, 47, 178, 202, 223, 129, 149, 239, 210, 172, 189, 208, 164, 222, 168, 234, 199, 119, 85, 79, 181, 2, 17, 0, 0, 0, 4, 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