← previous blocknext block →recent activity
Analyzing
Block #96,639,212
17 transactions · 16 stateful · 2026-08-17 01:00:05 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,639,212 · 17 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
1w02w13w04w05w16w17w28w39w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
4 touches
1 conflict
0x62811193…1867
0x2b46c0…1669
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
4 touches
1 conflict
0x7a89325a…d7e0
0x2b46c0…1669
4 touches
1 conflict
0x8b2c44b4…7e59
0x2b46c0…1669
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
6 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity