Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccadeffd03c99f7e2804d99efc58b0d332554d42337b9aa83a1616afaddd317c

Tx prefix hash: a1fdec16e558520cbb01c75837ff10549e7be8c6bcc46e0524e9423415ea4100
Tx public key: 23bfd40990b9a4e67c0951c794ba2c4e56c00bd979a04c31f0f6accd7664cd09
Timestamp: 1639415313 Timestamp [UCT]: 2021-12-13 17:08:33 Age [y:d:h:m:s]: 03:092:07:36:54
Block: 394749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 844736 RingCT/type: yes/0
Extra: 0123bfd40990b9a4e67c0951c794ba2c4e56c00bd979a04c31f0f6accd7664cd09021100000003eaa12622000000000000000000

1 output(s) for total of 30.201815767000 dcy

stealth address amount amount idx
00: 9c7e20b0afaa97c3b762825249307f8700dff29da7f789fc4c88be57e65a4bfd 30.201815767000 792442 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": 394759, "vin": [ { "gen": { "height": 394749 } } ], "vout": [ { "amount": 30201815767, "target": { "key": "9c7e20b0afaa97c3b762825249307f8700dff29da7f789fc4c88be57e65a4bfd" } } ], "extra": [ 1, 35, 191, 212, 9, 144, 185, 164, 230, 124, 9, 81, 199, 148, 186, 44, 78, 86, 192, 11, 217, 121, 160, 76, 49, 240, 246, 172, 205, 118, 100, 205, 9, 2, 17, 0, 0, 0, 3, 234, 161, 38, 34, 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