Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 381b38bc9d993719d974176e1779227fe9b1c653dee5f8b7c4e3b01217584687

Tx prefix hash: 0210424713c0696e8d4255bdc95cf0c0b6eb1c7c13e35b2b211ac8caa71dd139
Tx public key: 7ba3588cc5b5410ea2733d1201c0d6c8d65a5f291d0ebf2b8802e2f856fa9528
Timestamp: 1574526669 Timestamp [UCT]: 2019-11-23 16:31:09 Age [y:d:h:m:s]: 05:343:05:55:14
Block: 15712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1385799 RingCT/type: yes/0
Extra: 017ba3588cc5b5410ea2733d1201c0d6c8d65a5f291d0ebf2b8802e2f856fa9528021100000006f95225a5000000000000000000

1 output(s) for total of 544.428064968000 dcy

stealth address amount amount idx
00: 3c0b0e2bc7c3b543aa7a6797cf1bb83ccd7a182d125ad57a6b95772792fbc2be 544.428064968000 21278 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": 15722, "vin": [ { "gen": { "height": 15712 } } ], "vout": [ { "amount": 544428064968, "target": { "key": "3c0b0e2bc7c3b543aa7a6797cf1bb83ccd7a182d125ad57a6b95772792fbc2be" } } ], "extra": [ 1, 123, 163, 88, 140, 197, 181, 65, 14, 162, 115, 61, 18, 1, 192, 214, 200, 214, 90, 95, 41, 29, 14, 191, 43, 136, 2, 226, 248, 86, 250, 149, 40, 2, 17, 0, 0, 0, 6, 249, 82, 37, 165, 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