Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a529b090577811a7b71e594207c991bc02b9f65882fdabf4466ccb4af1e76d0

Tx prefix hash: 60f7fa1cfe33ac8b8156a50deccf53892ef13fd1a745f3a53e4128bcb480ae0c
Tx public key: 98a6dc5898f9d2072ba7cf26ad9d4699218868bc13a8f804a53a1167aac043aa
Timestamp: 1581213721 Timestamp [UCT]: 2020-02-09 02:02:01 Age [y:d:h:m:s]: 04:295:20:11:57
Block: 60980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103577 RingCT/type: yes/0
Extra: 0198a6dc5898f9d2072ba7cf26ad9d4699218868bc13a8f804a53a1167aac043aa02110000001c4943cd9f000000000000000000

1 output(s) for total of 385.432882460000 dcy

stealth address amount amount idx
00: aae8487f5e8d898de7fdfd5ec242f3a3a6ab59f58d1a920c1af1d53bc9e6ffe7 385.432882460000 112413 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": 60990, "vin": [ { "gen": { "height": 60980 } } ], "vout": [ { "amount": 385432882460, "target": { "key": "aae8487f5e8d898de7fdfd5ec242f3a3a6ab59f58d1a920c1af1d53bc9e6ffe7" } } ], "extra": [ 1, 152, 166, 220, 88, 152, 249, 210, 7, 43, 167, 207, 38, 173, 157, 70, 153, 33, 136, 104, 188, 19, 168, 248, 4, 165, 58, 17, 103, 170, 192, 67, 170, 2, 17, 0, 0, 0, 28, 73, 67, 205, 159, 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