Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c68adfcdfbd54f2a56fd6c19a613e0fd4f6440618417dc25b1fd1890f612d25

Tx prefix hash: 8fd22109ce03bbad67bba40fcc93d171dbad346fb2f77696178eb945d62a1094
Tx public key: e5d8a457d66128b7667a80f91d23475340daf377c1a55b7f928eb7a196993f01
Timestamp: 1751136691 Timestamp [UCT]: 2025-06-28 18:51:31 Age [y:d:h:m:s]: 00:140:07:36:39
Block: 1314696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98383 RingCT/type: yes/0
Extra: 01e5d8a457d66128b7667a80f91d23475340daf377c1a55b7f928eb7a196993f010211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3585840920b97dd96c57ef2513d171b319e6a87612fda3c6f6b68ee5eac88a87 0.600000000000 1802347 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": 1314706, "vin": [ { "gen": { "height": 1314696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3585840920b97dd96c57ef2513d171b319e6a87612fda3c6f6b68ee5eac88a87" } } ], "extra": [ 1, 229, 216, 164, 87, 214, 97, 40, 183, 102, 122, 128, 249, 29, 35, 71, 83, 64, 218, 243, 119, 193, 165, 91, 127, 146, 142, 183, 161, 150, 153, 63, 1, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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