← previous blocknext block →recent activity
Analyzing
Block #96,142,648
10 transactions · 9 stateful · 2026-08-15 07:22:17 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,142,648 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x362894e6…669f
0x34b655…2a6f
4 touches
1 conflict
0xb0cc22f4…af33
0x34b655…2a6f
4 touches
1 conflict
0xeeae09af…74f2
0x1efe02…37d6
2 touches
0 conflicts
0x1a5d321d…a474
0x34b655…2a6f
2 touches
0 conflicts
0x3b660503…f1fe
0x754704…b603
2 touches
0 conflicts
0x5512f9f8…dbe3
0x754704…b603
2 touches
0 conflicts
0xc96ef8cc…ff2e
0x754704…b603
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 0x1d351a9b20…2df2dd
Audit this contract →
← previous block·next block →recent activity