Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378d9c8dd34c04ad7d3038c218cf8bd0350a7dd55fad832fe457dea0e0fe36b4

Tx prefix hash: 6578cf5af8bfe9112c79ccaa407e7e8d704066699a6e5c411925c0f8064c1e1e
Tx public key: afe22134c6cb596fd1c9eae4d8600ac9d033a43c260a4f9ee5a14b82a871e400
Timestamp: 1750054934 Timestamp [UCT]: 2025-06-16 06:22:14 Age [y:d:h:m:s]: 00:230:06:11:57
Block: 1306058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162266 RingCT/type: yes/0
Extra: 01afe22134c6cb596fd1c9eae4d8600ac9d033a43c260a4f9ee5a14b82a871e40002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3c963338b98021bd776aafd3afa2f493263826a2dfd551590b888c056e5ca8b 0.600000000000 1793661 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": 1306068, "vin": [ { "gen": { "height": 1306058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3c963338b98021bd776aafd3afa2f493263826a2dfd551590b888c056e5ca8b" } } ], "extra": [ 1, 175, 226, 33, 52, 198, 203, 89, 111, 209, 201, 234, 228, 216, 96, 10, 201, 208, 51, 164, 60, 38, 10, 79, 158, 229, 161, 75, 130, 168, 113, 228, 0, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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