← previous blocknext block →recent activity
Analyzing
Block #96,623,019
20 transactions · 17 stateful · 2026-08-16 23:38:39 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,623,019 · 20 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
1w04w07w18w111w112w213w316w417w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdbe6b59…f6d8
0x34b655…2a6f
10 touches
10 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x33649c4f…b327
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xbdbe6b59da…0cf6d8
Audit this contract →
← previous block·next block →recent activity