← previous blocknext block →recent activity
Analyzing
Block #94,230,101
18 transactions · 18 stateful · 2026-08-08 14:33:32 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,230,101 · 18 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
1w02w04w05w16w07w18w19w212w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0x3371a69b…441e
0x34b655…2a6f
6 touches
3 conflicts
0x34cdb3c2…96d2
0x34b655…2a6f
4 touches
1 conflict
0x449bb837…a6a8
0x34b655…2a6f
4 touches
1 conflict
0x5224bec0…0675
0x34b655…2a6f
4 touches
1 conflict
0x8c7eac39…f34d
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity