← previous blocknext block →recent activity
Analyzing
Block #95,624,222
12 transactions · 9 stateful · 2026-08-13 11:53:09 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,624,222 · 12 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
5w06w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45f398c8…c1cb
0x34b655…2a6f
4 touches
1 conflict
0xe131df52…7554
0x34b655…2a6f
4 touches
1 conflict
0xe4a37d08…ffec
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x2b64d0d7…af06
0x34b655…2a6f
4 touches
1 conflict
0x6704b474…2d8d
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
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 0x45f398c846…0ec1cb
Audit this contract →
← previous block·next block →recent activity