← previous blocknext block →recent activity
Analyzing
Block #96,363,246
15 transactions · 14 stateful · 2026-08-16 01:51:47 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,363,246 · 15 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
2w03w04w16w17w08w29w210w011w112w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6848351…2238
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0x3464bbc5…a323
0xa6afd3…d132
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0x2bcdd4a1…3d3a
0x34b655…2a6f
4 touches
1 conflict
0x659be084…91fb
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xa68483512f…c32238
Audit this contract →
← previous block·next block →recent activity