Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 083a4ed497f41e29a9d50379914555e5c77673eeea1811ee182f14bfa96fa142

Tx prefix hash: b02a7311db9e29e02929b9d93f233a5520648912fbfb30ea01dfcb54ba5d1675
Tx public key: 7b29440e5f4ca979bd1459815cd3a0e3f01c310f376d8daa49997a7f8c7ff84a
Timestamp: 1710373587 Timestamp [UCT]: 2024-03-13 23:46:27 Age [y:d:h:m:s]: 01:094:03:16:30
Block: 977764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328207 RingCT/type: yes/0
Extra: 017b29440e5f4ca979bd1459815cd3a0e3f01c310f376d8daa49997a7f8c7ff84a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91b133970b7f4b589574c4e704085185a3e92b5195b755ea62718e3338294b37 0.600000000000 1437771 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": 977774, "vin": [ { "gen": { "height": 977764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91b133970b7f4b589574c4e704085185a3e92b5195b755ea62718e3338294b37" } } ], "extra": [ 1, 123, 41, 68, 14, 95, 76, 169, 121, 189, 20, 89, 129, 92, 211, 160, 227, 240, 28, 49, 15, 55, 109, 141, 170, 73, 153, 122, 127, 140, 127, 248, 74, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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