← previous blocknext block →recent activity
Analyzing
Block #96,307,833
19 transactions · 19 stateful · 2026-08-15 21:13:06 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,307,833 · 19 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
1w02w13w04w17w08w09w110w011w212w313w314w015w416w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0x427dec7f…61c6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5827be1e…2a9f
0x34b655…2a6f
4 touches
1 conflict
0x73670e81…2813
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
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
10 conflicts on slot 0xafb8e71eb0…ec9285
Audit this contract →
← previous block·next block →recent activity