Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2fca5d23a1d217be29f89f8a95c21837f2f8e6d27c762738c17b05b8274ca09

Tx prefix hash: a93860e7d95a0c27e97312f48db012daf7d54e65cd386719873027d162b0b0c1
Tx public key: a34ead9c86be8004470486c8b888fa0df4b27a88bf87c7f77b7a424225750b95
Timestamp: 1748560019 Timestamp [UCT]: 2025-05-29 23:06:59 Age [y:d:h:m:s]: 00:244:09:49:32
Block: 1293797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172280 RingCT/type: yes/0
Extra: 01a34ead9c86be8004470486c8b888fa0df4b27a88bf87c7f77b7a424225750b95021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 350443724b5d28172ecf0655394df144bc794f0188d53ea6c6a9ec48c76a5fd2 0.600000000000 1781292 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": 1293807, "vin": [ { "gen": { "height": 1293797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "350443724b5d28172ecf0655394df144bc794f0188d53ea6c6a9ec48c76a5fd2" } } ], "extra": [ 1, 163, 78, 173, 156, 134, 190, 128, 4, 71, 4, 134, 200, 184, 136, 250, 13, 244, 178, 122, 136, 191, 135, 199, 247, 123, 122, 66, 66, 37, 117, 11, 149, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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