Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2ad7ed22301f62466c07324116e18da0255537322ce81d56cd28f36813fdcb

Tx prefix hash: 8b4c7e3e8c8f144104ce7f934cee6257dc61678f50111542d1cab08c2fe942cd
Tx public key: 5f851fec6f6503cb926c13b076e7d6c79a1090151af7397df8b578bb7f2422b4
Timestamp: 1712373153 Timestamp [UCT]: 2024-04-06 03:12:33 Age [y:d:h:m:s]: 00:223:07:43:30
Block: 994285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159915 RingCT/type: yes/0
Extra: 015f851fec6f6503cb926c13b076e7d6c79a1090151af7397df8b578bb7f2422b402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2b608649e00749bf947f9af7660def5388643de8ae7118536dc1ae02804cabf 0.600000000000 1454687 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": 994295, "vin": [ { "gen": { "height": 994285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2b608649e00749bf947f9af7660def5388643de8ae7118536dc1ae02804cabf" } } ], "extra": [ 1, 95, 133, 31, 236, 111, 101, 3, 203, 146, 108, 19, 176, 118, 231, 214, 199, 154, 16, 144, 21, 26, 247, 57, 125, 248, 181, 120, 187, 127, 36, 34, 180, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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