← previous blocknext block →recent activity
Analyzing
Block #95,648,900
20 transactions · 19 stateful · 2026-08-13 13:57:17 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,648,900 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w08w212w113w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda366b17…f884
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x342222e8…2ec4
0x34b655…2a6f
6 touches
3 conflicts
0xb0608dfe…083d
0x34b655…2a6f
6 touches
3 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xf17c63a1…a36b
0x34b655…2a6f
4 touches
1 conflict
0xbd70971b…1547
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 0xda366b1736…d4f884
Audit this contract →
← previous block·next block →recent activity