← previous blocknext block →recent activity
Analyzing
Block #96,220,970
10 transactions · 7 stateful · 2026-08-15 13:56:12 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,220,970 · 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
5w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f57bd36…7796
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x17a14264…f419
0x34b655…2a6f
4 touches
1 conflict
0xf43f342c…614b
0x34b655…2a6f
4 touches
1 conflict
0x109c2330…f629
0x34b655…2a6f
2 touches
0 conflicts
0x12b9eaa0…a650
0x34b655…2a6f
2 touches
0 conflicts
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 0x3f57bd366a…ad7796
Audit this contract →
← previous block·next block →recent activity