Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97f0c2827f6932f56b95aa1e7488e17b24c498164b3a72d78e828349bbc53b2d

Tx prefix hash: 0b85c23c3ffe2e930b24194beccfabbadb612716456620e8122eef0a829dd595
Tx public key: 0b82e20f3defb0466dcbd9b626772632502629702f2298d4b5e8d01fccf4ec6f
Timestamp: 1733390944 Timestamp [UCT]: 2024-12-05 09:29:04 Age [y:d:h:m:s]: 00:143:22:10:38
Block: 1168475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102674 RingCT/type: yes/0
Extra: 010b82e20f3defb0466dcbd9b626772632502629702f2298d4b5e8d01fccf4ec6f021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25c1e77135daa8d12a0732d667f32ce68a83d40c0fcec17936610cd502c792f9 0.600000000000 1654184 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": 1168485, "vin": [ { "gen": { "height": 1168475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25c1e77135daa8d12a0732d667f32ce68a83d40c0fcec17936610cd502c792f9" } } ], "extra": [ 1, 11, 130, 226, 15, 61, 239, 176, 70, 109, 203, 217, 182, 38, 119, 38, 50, 80, 38, 41, 112, 47, 34, 152, 212, 181, 232, 208, 31, 204, 244, 236, 111, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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