← previous blocknext block →recent activity
Analyzing
Block #96,114,354
13 transactions · 13 stateful · 2026-08-15 04:59:55 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,114,354 · 13 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
1w03w14w15w06w110w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87292c3e…5e25
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x81da6711…3869
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0ae2991a…6a02
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x80fc7c2a…b248
0x34b655…2a6f
4 touches
1 conflict
0xfe3d37ee…6e67
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 0x87292c3e84…235e25
Audit this contract →
← previous block·next block →recent activity