← previous blocknext block →recent activity
Analyzing
Block #93,664,690
26 transactions · 24 stateful · 2026-08-06 15:05:29 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,664,690 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w010w012w113w214w316w019w120w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
8 touches
6 conflicts
0x973d4fba…8462
0x34b655…2a6f
6 touches
3 conflicts
0xd676e291…3ecf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity