← previous blocknext block →recent activity
Analyzing
Block #95,904,084
17 transactions · 14 stateful · 2026-08-14 11:22:02 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,904,084 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0xdbe0864c…4167
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
0x34b655…2a6f
4 touches
1 conflict
0x5906754f…b584
0x34b655…2a6f
2 touches
0 conflicts
0x82f1549d…82c3
0x34b655…2a6f
2 touches
0 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x31616f9701…df1acc
Audit this contract →
← previous block·next block →recent activity