Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fa2dbeefec02e80ef5ffe505fe5614b3cfc6e5a274171c6741b827bb4b7beb0

Tx prefix hash: 03092a530653eadd1d34c28ae7591fe119e65ca6e2a6cc2307b0a6fa6a677a7c
Tx public key: 086557802fdd962bc838130b414d8d28b7c247f956ce8e45fbeab67fd875e5d8
Timestamp: 1764019448 Timestamp [UCT]: 2025-11-24 21:24:08 Age [y:d:h:m:s]: 00:062:16:41:45
Block: 1419370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44712 RingCT/type: yes/0
Extra: 01086557802fdd962bc838130b414d8d28b7c247f956ce8e45fbeab67fd875e5d802110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 689735fa31878eba48c1db81689addd2c2a793ae118f0249f24c0076b6f40b65 0.600000000000 1907907 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": 1419380, "vin": [ { "gen": { "height": 1419370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "689735fa31878eba48c1db81689addd2c2a793ae118f0249f24c0076b6f40b65" } } ], "extra": [ 1, 8, 101, 87, 128, 47, 221, 150, 43, 200, 56, 19, 11, 65, 77, 141, 40, 183, 194, 71, 249, 86, 206, 142, 69, 251, 234, 182, 127, 216, 117, 229, 216, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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