← previous blocknext block →recent activity
Analyzing
Block #92,241,929
10 transactions · 10 stateful · 2026-08-01 15:47:39 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,241,929 · 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
2w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf6c3e51…c493
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x73ba144a…e0de
0x34b655…2a6f
4 touches
1 conflict
0x167ca698…e836
0x34b655…2a6f
2 touches
0 conflicts
0x18d306ad…d8f4
0x34b655…2a6f
2 touches
0 conflicts
0x1f6f8ff8…a5d4
0x34b655…2a6f
2 touches
0 conflicts
0x1f6f8ff8…a5d5
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 0xdf6c3e5189…c5c493
Audit this contract →
← previous block·next block →recent activity