Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26b762cd94626d4586e2467053c8c4efcae50353273dc2b3d1ca1c6473054fc3

Tx prefix hash: 00892fd36912a46691d345c6372bf1835d1a82a371ad7e3feff59ed65dc82b92
Tx public key: a0c785c3c4d9041f9e421fb3aa7bfc3068b7ea9086c29ca7f58785e00fa3f167
Timestamp: 1748661897 Timestamp [UCT]: 2025-05-31 03:24:57 Age [y:d:h:m:s]: 00:179:11:00:34
Block: 1294633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125958 RingCT/type: yes/0
Extra: 01a0c785c3c4d9041f9e421fb3aa7bfc3068b7ea9086c29ca7f58785e00fa3f16702110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36ec9c2c27a6ed368a8ac569ad3a686ed37c842293154e6e4b2419fcfa5809b7 0.600000000000 1782128 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": 1294643, "vin": [ { "gen": { "height": 1294633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36ec9c2c27a6ed368a8ac569ad3a686ed37c842293154e6e4b2419fcfa5809b7" } } ], "extra": [ 1, 160, 199, 133, 195, 196, 217, 4, 31, 158, 66, 31, 179, 170, 123, 252, 48, 104, 183, 234, 144, 134, 194, 156, 167, 245, 135, 133, 224, 15, 163, 241, 103, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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