← previous blocknext block →recent activity
Analyzing
Block #96,036,971
11 transactions · 10 stateful · 2026-08-14 22:30:44 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,036,971 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bfc672f…4d28
0x34b655…2a6f
6 touches
3 conflicts
0xd7d3cccb…fd18
0x34b655…2a6f
6 touches
3 conflicts
0xab5344c9…3de7
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0x3c95c2c0…b38d
0x34b655…2a6f
4 touches
3 conflicts
0xc824469a…641d
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 0x2bfc672ff5…fc4d28
Audit this contract →
← previous block·next block →recent activity