Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3b9f2178ceeabdf4f5cc73a714b90f071c15ac09992414c4bd9b7d444af4e3

Tx prefix hash: 78f350c62679bf1586d42d7ff7ff0628b6ae377ecd34f1aba74ed6d6f33a718f
Tx public key: 12768825b07be17bead12f8df01363cf58b179284ebc7c202d758859b951d8e5
Timestamp: 1735419362 Timestamp [UCT]: 2024-12-28 20:56:02 Age [y:d:h:m:s]: 00:108:18:24:48
Block: 1185252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77541 RingCT/type: yes/0
Extra: 0112768825b07be17bead12f8df01363cf58b179284ebc7c202d758859b951d8e502110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c4153050c45716b11457df1803449d7669c0dbcce67ff49c0e5f390a1fd84ea 0.600000000000 1671719 of 15

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": 1185262, "vin": [ { "gen": { "height": 1185252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c4153050c45716b11457df1803449d7669c0dbcce67ff49c0e5f390a1fd84ea" } } ], "extra": [ 1, 18, 118, 136, 37, 176, 123, 225, 123, 234, 209, 47, 141, 240, 19, 99, 207, 88, 177, 121, 40, 78, 188, 124, 32, 45, 117, 136, 89, 185, 81, 216, 229, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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