← previous blocknext block →recent activity
Analyzing
Block #96,666,722
10 transactions · 9 stateful · 2026-08-17 03:18:27 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,666,722 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x068a8ba7…7c92
0x34b655…2a6f
4 touches
1 conflict
0x0df76185…266f
0x34b655…2a6f
4 touches
1 conflict
0x20d0c78a…d1ae
0x34b655…2a6f
4 touches
1 conflict
0x2debe664…1818
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x410376a5…b133
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
1 conflict on slot 0x02d895f0dc…af2b93
Audit this contract →
← previous block·next block →recent activity