Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3a3afa3703e89637ee3d3523deeea1f7cf6996516bceb7b597b05530633714b

Tx prefix hash: ec06881c9117c7152bd580b36ea62f3afb678dd7f3a8b23a5e532bbf2456859f
Tx public key: b58e5c3cc0a13c0d6493bfb35d7cabb89f86325682d659e60bee9c0096909834
Timestamp: 1581091785 Timestamp [UCT]: 2020-02-07 16:09:45 Age [y:d:h:m:s]: 05:069:14:24:07
Block: 60726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201804 RingCT/type: yes/0
Extra: 01b58e5c3cc0a13c0d6493bfb35d7cabb89f86325682d659e60bee9c009690983402110000000156c366d3000000000000000000

1 output(s) for total of 386.199936855000 dcy

stealth address amount amount idx
00: 06a5cafd73189bcc44c5fd854f7a3d2901f2d73c9beb2b385e1191520108d7e6 386.199936855000 111791 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": 60736, "vin": [ { "gen": { "height": 60726 } } ], "vout": [ { "amount": 386199936855, "target": { "key": "06a5cafd73189bcc44c5fd854f7a3d2901f2d73c9beb2b385e1191520108d7e6" } } ], "extra": [ 1, 181, 142, 92, 60, 192, 161, 60, 13, 100, 147, 191, 179, 93, 124, 171, 184, 159, 134, 50, 86, 130, 214, 89, 230, 11, 238, 156, 0, 150, 144, 152, 52, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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