Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b0fec9d1130ac4b79013955c851e7392818a930854d8e848ba1fc5e5a485fce

Tx prefix hash: f9da26444354d311e63501897dafb0c765d7d6a463008a26677c82a8f997c59a
Tx public key: 0a9993a50b216b924db3d70e94f8c11695a630a72bae72a178fa7875181d89b7
Timestamp: 1701756391 Timestamp [UCT]: 2023-12-05 06:06:31 Age [y:d:h:m:s]: 01:340:17:45:06
Block: 906295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502411 RingCT/type: yes/0
Extra: 010a9993a50b216b924db3d70e94f8c11695a630a72bae72a178fa7875181d89b702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.609632931000 dcy

stealth address amount amount idx
00: 0e0da59b5178ed9e80d556dda8b303a001c3d12ace9c485296b47e4dc37204dc 0.609632931000 1363222 of 0

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": 906305, "vin": [ { "gen": { "height": 906295 } } ], "vout": [ { "amount": 609632931, "target": { "key": "0e0da59b5178ed9e80d556dda8b303a001c3d12ace9c485296b47e4dc37204dc" } } ], "extra": [ 1, 10, 153, 147, 165, 11, 33, 107, 146, 77, 179, 215, 14, 148, 248, 193, 22, 149, 166, 48, 167, 43, 174, 114, 161, 120, 250, 120, 117, 24, 29, 137, 183, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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