Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ca5ebec3532501d3a96c33925f21ef3dadb1eb47d207d55830a021f5cf1e9c3

Tx prefix hash: cf6a22400230e025ec946c6d6c0a1503c79259e9abdf25fbc8003c60ea90e288
Tx public key: da4c8a0c4acd2f66480733d070f8dcba7965b58f34b83c61f75b42e8a8cc82d2
Timestamp: 1699611631 Timestamp [UCT]: 2023-11-10 10:20:31 Age [y:d:h:m:s]: 01:363:01:07:30
Block: 888534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518370 RingCT/type: yes/0
Extra: 01da4c8a0c4acd2f66480733d070f8dcba7965b58f34b83c61f75b42e8a8cc82d202110000000833af99f4000000000000000000

1 output(s) for total of 0.698100598000 dcy

stealth address amount amount idx
00: e1c5ef1aedcf0e6512d561238d036a05d97819ed807fb6011d3b4ae2eba8f01c 0.698100598000 1344481 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": 888544, "vin": [ { "gen": { "height": 888534 } } ], "vout": [ { "amount": 698100598, "target": { "key": "e1c5ef1aedcf0e6512d561238d036a05d97819ed807fb6011d3b4ae2eba8f01c" } } ], "extra": [ 1, 218, 76, 138, 12, 74, 205, 47, 102, 72, 7, 51, 208, 112, 248, 220, 186, 121, 101, 181, 143, 52, 184, 60, 97, 247, 91, 66, 232, 168, 204, 130, 210, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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