← previous blocknext block →recent activity
Analyzing
Block #96,665,323
21 transactions · 17 stateful · 2026-08-17 03:11:24 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,665,323 · 21 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
1w04w05w16w17w210w111w012w215w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
8 touches
6 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x03aa8b26…118a
0x34b655…2a6f
4 touches
1 conflict
0x4bccd149…7d0e
0x34b655…2a6f
4 touches
1 conflict
0x594dd01b…6c8b
0x34b655…2a6f
4 touches
1 conflict
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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
6 conflicts on slot 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity