← previous blocknext block →recent activity
Analyzing
Block #96,287,384
6 transactions · 5 stateful · 2026-08-15 19:30:15 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,287,384 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x00c89f9d…f5bf
0x34b655…2a6f
2 touches
0 conflicts
0x056903ee…8bc2
0x34b655…2a6f
2 touches
0 conflicts
0x143c16d2…5e4d
0x34b655…2a6f
2 touches
0 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
2 touches
0 conflicts
0x2e7a0c1d…caaf
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 0xa4e9800f4e…fc4ab1
Audit this contract →
← previous block·next block →recent activity