Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990366fed3481e5ffabe493937e55a132ee2dea0c495a959dd27f8c016dd2b2b

Tx prefix hash: b5887343ceddb94ec13a3d0b536964c9d34708c9e95aa3c218e2a034c69ceb71
Tx public key: 232e6200bef6ae658fb3a6b69380cfd846e1f131be78dfad66c5022436e0d00c
Timestamp: 1713518619 Timestamp [UCT]: 2024-04-19 09:23:39 Age [y:d:h:m:s]: 00:356:02:33:12
Block: 1003819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254580 RingCT/type: yes/0
Extra: 01232e6200bef6ae658fb3a6b69380cfd846e1f131be78dfad66c5022436e0d00c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 140c37f506f029160a3d04537d4d3b39c906e1f04afbd4ec359197c71ae32bcf 0.600000000000 1464365 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": 1003829, "vin": [ { "gen": { "height": 1003819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "140c37f506f029160a3d04537d4d3b39c906e1f04afbd4ec359197c71ae32bcf" } } ], "extra": [ 1, 35, 46, 98, 0, 190, 246, 174, 101, 143, 179, 166, 182, 147, 128, 207, 216, 70, 225, 241, 49, 190, 120, 223, 173, 102, 197, 2, 36, 54, 224, 208, 12, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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