Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de089e08234b67cdbb1ff2a3e56f61bbba2c3a6d9f8cbce1ce4c1f880eb00acd

Tx prefix hash: 3e868cb606e32b530174bf7610ab30f0ef6c65888d370dbc9e081ecdc8e43083
Tx public key: 954efdf583e2a9b23fbc4d95b7fb29b080f55762a3e20d80c23925c14743833a
Timestamp: 1705767255 Timestamp [UCT]: 2024-01-20 16:14:15 Age [y:d:h:m:s]: 01:116:14:55:42
Block: 939530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344477 RingCT/type: yes/0
Extra: 01954efdf583e2a9b23fbc4d95b7fb29b080f55762a3e20d80c23925c14743833a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f55d7b6f05cf2bc2c71c790ff3b5709d9c8e5f10883174a5b9935e74b32ddeef 0.600000000000 1397638 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": 939540, "vin": [ { "gen": { "height": 939530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f55d7b6f05cf2bc2c71c790ff3b5709d9c8e5f10883174a5b9935e74b32ddeef" } } ], "extra": [ 1, 149, 78, 253, 245, 131, 226, 169, 178, 63, 188, 77, 149, 183, 251, 41, 176, 128, 245, 87, 98, 163, 226, 13, 128, 194, 57, 37, 193, 71, 67, 131, 58, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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