Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adc34c7f18e6640a94fa6b5465f955be596af5bed6fed406d82f5cc3710a7251

Tx prefix hash: 505280860e4d9a83e63f34e1ea0573f9cba946ade028785c70be5bf0e84b55d5
Tx public key: ab101b89e058514783d25f94d9f2809cc1c602c3079eb44d689c2cc953fcc9e0
Timestamp: 1752802299 Timestamp [UCT]: 2025-07-18 01:31:39 Age [y:d:h:m:s]: 00:198:08:55:10
Block: 1327781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140484 RingCT/type: yes/0
Extra: 01ab101b89e058514783d25f94d9f2809cc1c602c3079eb44d689c2cc953fcc9e0021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0447dbd29ffb0ad6e1a501944bfaa49de5d2d45a2d1ae30b021b1b11a68df1c1 0.600000000000 1815540 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": 1327791, "vin": [ { "gen": { "height": 1327781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0447dbd29ffb0ad6e1a501944bfaa49de5d2d45a2d1ae30b021b1b11a68df1c1" } } ], "extra": [ 1, 171, 16, 27, 137, 224, 88, 81, 71, 131, 210, 95, 148, 217, 242, 128, 156, 193, 198, 2, 195, 7, 158, 180, 77, 104, 156, 44, 201, 83, 252, 201, 224, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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