← previous blocknext block →recent activity
Analyzing
Block #96,619,739
17 transactions · 17 stateful · 2026-08-16 23:22:09 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,619,739 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w28w310w011w412w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x237fbe48…657b
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0x3d2c514e…49b1
0x34b655…2a6f
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x27b96981…ef48
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
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
3 conflicts on slot 0x237fbe487c…c6657b
Audit this contract →
← previous block·next block →recent activity