Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cea06a13624a34d0db1675d9f72112d696ba2a6aa60fb83d75f608a131b7f07

Tx prefix hash: 872ff41aa97e9e457b7b29bde23ee4b73c5bd72803fe33e8d26e743588ad157b
Tx public key: bcc30cc78c72a83c76e80e9dd15441c62bd6ab5670e960a2eb84fd718f8212a7
Timestamp: 1577191328 Timestamp [UCT]: 2019-12-24 12:42:08 Age [y:d:h:m:s]: 04:338:17:05:58
Block: 30698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131226 RingCT/type: yes/0
Extra: 01bcc30cc78c72a83c76e80e9dd15441c62bd6ab5670e960a2eb84fd718f8212a70211000000bbfeadaf7f000000000000000000

1 output(s) for total of 485.607788824000 dcy

stealth address amount amount idx
00: a77394b8bf5c8c484168d7e7558481a9b0b37d95dce740801924e78e56f0ed31 485.607788824000 50686 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": 30708, "vin": [ { "gen": { "height": 30698 } } ], "vout": [ { "amount": 485607788824, "target": { "key": "a77394b8bf5c8c484168d7e7558481a9b0b37d95dce740801924e78e56f0ed31" } } ], "extra": [ 1, 188, 195, 12, 199, 140, 114, 168, 60, 118, 232, 14, 157, 209, 84, 65, 198, 43, 214, 171, 86, 112, 233, 96, 162, 235, 132, 253, 113, 143, 130, 18, 167, 2, 17, 0, 0, 0, 187, 254, 173, 175, 127, 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