Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42c619d8074015db218a845ddaf50ac8b68fcde696c3cf5fcb2c7580ff193140

Tx prefix hash: d9d703af87bccac53adc53501bf3e73676463ca1d9cb15140f531cee33c9272a
Tx public key: 0e3da7ae112bcd63d5c4c00d70ed86ff2ee6a9274fd5b5f8a67a56d1eb24933a
Timestamp: 1762236235 Timestamp [UCT]: 2025-11-04 06:03:55 Age [y:d:h:m:s]: 00:006:15:30:27
Block: 1404593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4758 RingCT/type: yes/0
Extra: 010e3da7ae112bcd63d5c4c00d70ed86ff2ee6a9274fd5b5f8a67a56d1eb24933a021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cb1e0f446b7d5defd56bd3e241d994fa38d33ae83f09f468d0d7c09815b32f4 0.600000000000 1892952 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": 1404603, "vin": [ { "gen": { "height": 1404593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cb1e0f446b7d5defd56bd3e241d994fa38d33ae83f09f468d0d7c09815b32f4" } } ], "extra": [ 1, 14, 61, 167, 174, 17, 43, 205, 99, 213, 196, 192, 13, 112, 237, 134, 255, 46, 230, 169, 39, 79, 213, 181, 248, 166, 122, 86, 209, 235, 36, 147, 58, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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