Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5a5696831c3b399c67e27c0b7267af28b71795e7d6565ec0d0479ac32cdf4c7

Tx prefix hash: 0ec65d3d22131532afaad5f582f8f9d5848591296451cae61fab1bf32b95e74c
Tx public key: bba8f8a64eb82f27ae7d6d24aba2986bf768918ae6881d6aca153ceca558f78c
Timestamp: 1583641727 Timestamp [UCT]: 2020-03-08 04:28:47 Age [y:d:h:m:s]: 05:064:13:47:16
Block: 78752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201292 RingCT/type: yes/0
Extra: 01bba8f8a64eb82f27ae7d6d24aba2986bf768918ae6881d6aca153ceca558f78c0211000000126d997e00000000000000000000

1 output(s) for total of 336.560174564000 dcy

stealth address amount amount idx
00: ff6671243e0a0fb9128c0b92011fcdead6d7c2aa1bf6d58b27fdabc0626a69cb 336.560174564000 144222 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": 78762, "vin": [ { "gen": { "height": 78752 } } ], "vout": [ { "amount": 336560174564, "target": { "key": "ff6671243e0a0fb9128c0b92011fcdead6d7c2aa1bf6d58b27fdabc0626a69cb" } } ], "extra": [ 1, 187, 168, 248, 166, 78, 184, 47, 39, 174, 125, 109, 36, 171, 162, 152, 107, 247, 104, 145, 138, 230, 136, 29, 106, 202, 21, 60, 236, 165, 88, 247, 140, 2, 17, 0, 0, 0, 18, 109, 153, 126, 0, 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