Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fed7f59971bbb6aea5625d8d78e32005201d101f64be644f3da6269e9b2c26d

Tx prefix hash: e09facd1a7327b7baf3c8f5c2844dc8e5ea6806f808bfeb384b621ea849e75ed
Tx public key: ec84cb26aefab0227e9cedfe213f2b9758f5d5dab5101180f88e7195235ca33a
Timestamp: 1751732370 Timestamp [UCT]: 2025-07-05 16:19:30 Age [y:d:h:m:s]: 00:131:16:31:00
Block: 1319354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92486 RingCT/type: yes/0
Extra: 01ec84cb26aefab0227e9cedfe213f2b9758f5d5dab5101180f88e7195235ca33a0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc97f8d3a759a168d9b0e2dffdca7ee71405260b05b3524a9633d5637e15c10e 0.600000000000 1807045 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": 1319364, "vin": [ { "gen": { "height": 1319354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc97f8d3a759a168d9b0e2dffdca7ee71405260b05b3524a9633d5637e15c10e" } } ], "extra": [ 1, 236, 132, 203, 38, 174, 250, 176, 34, 126, 156, 237, 254, 33, 63, 43, 151, 88, 245, 213, 218, 181, 16, 17, 128, 248, 142, 113, 149, 35, 92, 163, 58, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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