Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c33204c974040beffe4724f5e97be3a9880c60b6c58031ff74615912d99fea

Tx prefix hash: 7998689c2bcbcea0961d14e1ba2b0ef4b59a737b9cce05863b125e7effcfe411
Tx public key: 05c8dd6ac47c767f1859b3d4c704d122e7b55c6fd65cdc7c7fed11426f69ae06
Timestamp: 1705572379 Timestamp [UCT]: 2024-01-18 10:06:19 Age [y:d:h:m:s]: 01:154:05:51:13
Block: 937926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371223 RingCT/type: yes/0
Extra: 0105c8dd6ac47c767f1859b3d4c704d122e7b55c6fd65cdc7c7fed11426f69ae0602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7e1dfde279d135fad86f34a1e0d5175479a9aaffb1d879ee8b507984b8ab383 0.600000000000 1395990 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": 937936, "vin": [ { "gen": { "height": 937926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7e1dfde279d135fad86f34a1e0d5175479a9aaffb1d879ee8b507984b8ab383" } } ], "extra": [ 1, 5, 200, 221, 106, 196, 124, 118, 127, 24, 89, 179, 212, 199, 4, 209, 34, 231, 181, 92, 111, 214, 92, 220, 124, 127, 237, 17, 66, 111, 105, 174, 6, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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