← previous blocknext block →recent activity
Analyzing
Block #96,025,962
10 transactions · 7 stateful · 2026-08-14 21:35:19 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,025,962 · 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
6w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26ec135b…9718
0x34b655…2a6f
4 touches
1 conflict
0x39126904…24d8
0x34b655…2a6f
4 touches
1 conflict
0x5fab7fbe…1ce5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xfa6c5c9a…573a
0x34b655…2a6f
4 touches
1 conflict
0x49c35ed6…0288
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a1
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 0x26ec135b60…939718
Audit this contract →
← previous block·next block →recent activity