← previous blocknext block →recent activity
Analyzing
Block #92,000,046
16 transactions · 10 stateful · 2026-07-31 19:31:09 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,000,046 · 16 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8b2ce22…7ded
0x34b655…2a6f
4 touches
1 conflict
0xd861b911…7b42
0x34b655…2a6f
4 touches
1 conflict
0x433ec3a1…a1e8
0x34b655…2a6f
4 touches
1 conflict
0x051aa260…b0a4
0x34b655…2a6f
2 touches
0 conflicts
0x11cecbd3…9d6c
0x34b655…2a6f
2 touches
0 conflicts
0x1d9cfc98…3057
0x34b655…2a6f
2 touches
0 conflicts
0x20317244…edb4
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0xf8b2ce2209…987ded
Audit this contract →
← previous block·next block →recent activity