Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27a9968a68870f8df1516550fa24af4d22fc93886018fc3a3b2267e3c3ed63f7

Tx prefix hash: 566fd15c2782fa4b4cdf87cc858a3c96866ddaafe7c5104e48aacce6725573b4
Tx public key: cb3adde93c0ca7df4593926da26311ef2e0db686b11dc87f8811aa38d8ebc541
Timestamp: 1574335238 Timestamp [UCT]: 2019-11-21 11:20:38 Age [y:d:h:m:s]: 04:363:11:03:23
Block: 13618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1142363 RingCT/type: yes/0
Extra: 01cb3adde93c0ca7df4593926da26311ef2e0db686b11dc87f8811aa38d8ebc54102110000000266a80d00000000000000000000

1 output(s) for total of 553.195704341000 dcy

stealth address amount amount idx
00: ba66a77d2cf9c5f8b6169cbd815148e07705923cf1adf1336121b409d5ab2333 553.195704341000 16338 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": 13628, "vin": [ { "gen": { "height": 13618 } } ], "vout": [ { "amount": 553195704341, "target": { "key": "ba66a77d2cf9c5f8b6169cbd815148e07705923cf1adf1336121b409d5ab2333" } } ], "extra": [ 1, 203, 58, 221, 233, 60, 12, 167, 223, 69, 147, 146, 109, 162, 99, 17, 239, 46, 13, 182, 134, 177, 29, 200, 127, 136, 17, 170, 56, 216, 235, 197, 65, 2, 17, 0, 0, 0, 2, 102, 168, 13, 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