Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19abe7e662ee28dff6297b5ceeb05e2ca4e0db80892f89fd3e0b3b293d378b34

Tx prefix hash: 0a9b3c7f0d5faa377f5d61708a611255259efc17f44dbc0e9913e4e0bfa087b7
Tx public key: 8310437cdb5f004c97d06ad426c2a9dc3ba3a1233ce05b2dc9824405a7772272
Timestamp: 1758379826 Timestamp [UCT]: 2025-09-20 14:50:26 Age [y:d:h:m:s]: 00:103:14:07:20
Block: 1372638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74171 RingCT/type: yes/0
Extra: 018310437cdb5f004c97d06ad426c2a9dc3ba3a1233ce05b2dc9824405a7772272021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbc8d7cf6001fa801999d7ae91e93dd70668ae8cb888585a55fbd29eb213b519 0.600000000000 1860723 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": 1372648, "vin": [ { "gen": { "height": 1372638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbc8d7cf6001fa801999d7ae91e93dd70668ae8cb888585a55fbd29eb213b519" } } ], "extra": [ 1, 131, 16, 67, 124, 219, 95, 0, 76, 151, 208, 106, 212, 38, 194, 169, 220, 59, 163, 161, 35, 60, 224, 91, 45, 201, 130, 68, 5, 167, 119, 34, 114, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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