Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad8a2b272bf637027fff7d1ddee83bd61a298767de1c1e1510a867bea18e7150

Tx prefix hash: 76b0e46e490c875f4ae6ca47efd8181ef1df48fc87444bffd275b181c5463dd6
Tx public key: cfb807ece7cb045e68e3555eef52a3cc4ccb0a8636acb30ec74b861211062f22
Timestamp: 1681237949 Timestamp [UCT]: 2023-04-11 18:32:29 Age [y:d:h:m:s]: 01:275:13:18:44
Block: 736439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458448 RingCT/type: yes/0
Extra: 01cfb807ece7cb045e68e3555eef52a3cc4ccb0a8636acb30ec74b861211062f220211000000065029cbac000000000000000000

1 output(s) for total of 2.227778999000 dcy

stealth address amount amount idx
00: b06c37f205cbc047a452f675b69a8a648c047dd5765fe0f30cd1f566cb2a8a82 2.227778999000 1182872 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": 736449, "vin": [ { "gen": { "height": 736439 } } ], "vout": [ { "amount": 2227778999, "target": { "key": "b06c37f205cbc047a452f675b69a8a648c047dd5765fe0f30cd1f566cb2a8a82" } } ], "extra": [ 1, 207, 184, 7, 236, 231, 203, 4, 94, 104, 227, 85, 94, 239, 82, 163, 204, 76, 203, 10, 134, 54, 172, 179, 14, 199, 75, 134, 18, 17, 6, 47, 34, 2, 17, 0, 0, 0, 6, 80, 41, 203, 172, 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