Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38d96b33a8c3a0b8f087125c74fe1c35c9070f274c4a8284d861770cd07a92e

Tx prefix hash: da43680bd4856c698214a5875d20d63aabfc9514de465bf0d5cbb25700eddc2a
Tx public key: 58e822efe5fc898615ece7ffa1f0ee3ed257f8a2c32f7a1454e0e27fc336c992
Timestamp: 1758219992 Timestamp [UCT]: 2025-09-18 18:26:32 Age [y:d:h:m:s]: 00:095:21:39:00
Block: 1371306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68656 RingCT/type: yes/0
Extra: 0158e822efe5fc898615ece7ffa1f0ee3ed257f8a2c32f7a1454e0e27fc336c992021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c292ee79345302c4bb97b7de6f52e4373c9f510c1e2a767427050c90955c8c96 0.600000000000 1859383 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": 1371316, "vin": [ { "gen": { "height": 1371306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c292ee79345302c4bb97b7de6f52e4373c9f510c1e2a767427050c90955c8c96" } } ], "extra": [ 1, 88, 232, 34, 239, 229, 252, 137, 134, 21, 236, 231, 255, 161, 240, 238, 62, 210, 87, 248, 162, 195, 47, 122, 20, 84, 224, 226, 127, 195, 54, 201, 146, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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