← previous blocknext block →recent activity
Analyzing
Block #92,526,270
12 transactions · 10 stateful · 2026-08-02 15:37:41 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,526,270 · 12 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
2w04w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdf616f1…d568
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa787d248…0c44
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1b27e0c6…96d1
0x065c9d…c394
2 touches
0 conflicts
0x9f97d127…a8de
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
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 0xbdf616f1b7…dcd568
Audit this contract →
← previous block·next block →recent activity