Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be48916a067df4bd7c24f3e22cfa340bc6c692de66a259f8e84b0282beb44ba

Tx prefix hash: 8f92edbdddacc4b6371db0817c72ff9e82a0c31491159adfb99748e8cb53eb53
Tx public key: 9f014471edd6a47073fdcc5e0e5b4a810b5cb35e60fcd6c85a44971eb2f9724a
Timestamp: 1636074908 Timestamp [UCT]: 2021-11-05 01:15:08 Age [y:d:h:m:s]: 03:001:10:24:19
Block: 367548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 779513 RingCT/type: yes/0
Extra: 019f014471edd6a47073fdcc5e0e5b4a810b5cb35e60fcd6c85a44971eb2f9724a021100000001a272b9cb000000000000000000

1 output(s) for total of 37.167324332000 dcy

stealth address amount amount idx
00: 41e04a6a0f1acd5c1e57328b9459ceca2efa87be36deb9ce0f5d3f06ee221ab0 37.167324332000 745766 of 0

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": 367558, "vin": [ { "gen": { "height": 367548 } } ], "vout": [ { "amount": 37167324332, "target": { "key": "41e04a6a0f1acd5c1e57328b9459ceca2efa87be36deb9ce0f5d3f06ee221ab0" } } ], "extra": [ 1, 159, 1, 68, 113, 237, 214, 164, 112, 115, 253, 204, 94, 14, 91, 74, 129, 11, 92, 179, 94, 96, 252, 214, 200, 90, 68, 151, 30, 178, 249, 114, 74, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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