← previous blocknext block →recent activity
Analyzing
Block #92,547,964
8 transactions · 7 stateful · 2026-08-02 17:26:47 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,547,964 · 8 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
2w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c1d804e…835c
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0xc8155427…d542
0x34b655…2a6f
4 touches
1 conflict
0x034def5d…8368
0x34b655…2a6f
2 touches
0 conflicts
0x11bfd8ff…c326
0x34b655…2a6f
2 touches
0 conflicts
0x1b244003…c9cf
0x34b655…2a6f
2 touches
0 conflicts
0x1b244003…c9d0
0x34b655…2a6f
2 touches
0 conflicts
0x2656757d…54e8
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 0x7c1d804e88…15835c
Audit this contract →
← previous block·next block →recent activity