Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe9c8e7d23910bf72aaea8d14ace59b40623959a78b9cc9d868c84c05f502268

Tx prefix hash: acb09716e712d45676fe85249156723807691d40f239cd7a9376a3e5552aaeee
Tx public key: f61f975490d9e3fb002511da687b22cbc72c18aed8f8b585a0cffecc06faadd1
Timestamp: 1764343678 Timestamp [UCT]: 2025-11-28 15:27:58 Age [y:d:h:m:s]: 00:041:02:37:44
Block: 1422055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29446 RingCT/type: yes/0
Extra: 01f61f975490d9e3fb002511da687b22cbc72c18aed8f8b585a0cffecc06faadd1021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93a3d92f1ee60fc3b74049a94caff2361d9f5d764a565f44ae80ec39f7607fb9 0.600000000000 1910620 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": 1422065, "vin": [ { "gen": { "height": 1422055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93a3d92f1ee60fc3b74049a94caff2361d9f5d764a565f44ae80ec39f7607fb9" } } ], "extra": [ 1, 246, 31, 151, 84, 144, 217, 227, 251, 0, 37, 17, 218, 104, 123, 34, 203, 199, 44, 24, 174, 216, 248, 181, 133, 160, 207, 254, 204, 6, 250, 173, 209, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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