Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 086e8707b69c92629ec21f3f4d908bc1bdf4adae294770b4a6a23a4109f7f75e

Tx prefix hash: 4e5bdfa4f9f56d01c09b2d9078efea9b70e05b60f06b3709e584a5b7316b7da1
Tx public key: 67a2cbd7e87580e9fc43e08d9021ce1c569019bf9fcb99063834133cd2ea10e6
Timestamp: 1733541317 Timestamp [UCT]: 2024-12-07 03:15:17 Age [y:d:h:m:s]: 00:143:07:11:58
Block: 1169720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102241 RingCT/type: yes/0
Extra: 0167a2cbd7e87580e9fc43e08d9021ce1c569019bf9fcb99063834133cd2ea10e60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aef687ee2be16a51c478fb828df2af3af6c761d7c287ce6b03d5e95123f5b9ad 0.600000000000 1655443 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": 1169730, "vin": [ { "gen": { "height": 1169720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef687ee2be16a51c478fb828df2af3af6c761d7c287ce6b03d5e95123f5b9ad" } } ], "extra": [ 1, 103, 162, 203, 215, 232, 117, 128, 233, 252, 67, 224, 141, 144, 33, 206, 28, 86, 144, 25, 191, 159, 203, 153, 6, 56, 52, 19, 60, 210, 234, 16, 230, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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