Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea603a33c67aa49f66f61b6be13e0c9d26052f0505ac89050f55eb18d62ae284

Tx prefix hash: bc76439a4b4ffd3d793295fa059896741ac6b6229b0fd6cc1aa3b3420a5b6d1f
Tx public key: d0af51ea01c0b1b5092e4550a700d23183a53ab4a221e000795bb43cb840f8a9
Timestamp: 1581087007 Timestamp [UCT]: 2020-02-07 14:50:07 Age [y:d:h:m:s]: 04:330:05:37:32
Block: 60390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127712 RingCT/type: yes/0
Extra: 01d0af51ea01c0b1b5092e4550a700d23183a53ab4a221e000795bb43cb840f8a902110000003b7adf42d3000000000000000000

1 output(s) for total of 387.171765331000 dcy

stealth address amount amount idx
00: fd118a1f35f54f71ed9cb90f596641a420f2d631be6d8c2cacadf80449a553a1 387.171765331000 111314 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": 60400, "vin": [ { "gen": { "height": 60390 } } ], "vout": [ { "amount": 387171765331, "target": { "key": "fd118a1f35f54f71ed9cb90f596641a420f2d631be6d8c2cacadf80449a553a1" } } ], "extra": [ 1, 208, 175, 81, 234, 1, 192, 177, 181, 9, 46, 69, 80, 167, 0, 210, 49, 131, 165, 58, 180, 162, 33, 224, 0, 121, 91, 180, 60, 184, 64, 248, 169, 2, 17, 0, 0, 0, 59, 122, 223, 66, 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