← previous blocknext block →recent activity
Analyzing
Block #92,755,500
23 transactions · 23 stateful · 2026-08-03 10:51:45 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,755,500 · 23 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
3w05w112w014w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e19b081…7cec
0x34b655…2a6f
4 touches
1 conflict
0x852a0474…9701
0x34b655…2a6f
4 touches
1 conflict
0x9365e097…ff56
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
0x34b655…2a6f
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xdb067026…9eb8
0x2b46c0…1669
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 0x6e19b081e2…a37cec
Audit this contract →
← previous block·next block →recent activity