← previous blocknext block →recent activity
Analyzing
Block #96,590,130
22 transactions · 18 stateful · 2026-08-16 20:53:14 UTC
Parallelism
82/100
Blocked
61%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,590,130 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w19w110w211w212w313w214w216w319w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x93909ae2…df51
0x34b655…2a6f
6 touches
3 conflicts
0x77ea8cfe…b5c7
0x34b655…2a6f
6 touches
3 conflicts
0x6d16f6dc…6a62
0xd32edf…ff58
5 touches
3 conflicts
0x681dd2e1…ce40
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity