← previous blocknext block →recent activity
Analyzing
Block #96,625,389
14 transactions · 12 stateful · 2026-08-16 23:50:34 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,625,389 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
14 touches
21 conflicts
0x42275259…6050
0x34b655…2a6f
8 touches
6 conflicts
0xc2db6e7a…d074
0x34b655…2a6f
6 touches
3 conflicts
0x5fee7566…b8fd
0x34b655…2a6f
4 touches
1 conflict
0x60520483…e2ef
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7f2f4106…1c89
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
21 conflicts on slot 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity