← previous blocknext block →recent activity
Analyzing
Block #92,063,254
11 transactions · 11 stateful · 2026-08-01 00:49:03 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,063,254 · 11 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
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd065252…c2c8
0x34b655…2a6f
4 touches
1 conflict
0xf7fe9260…f369
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb42fe30c…8771
0x34b655…2a6f
4 touches
1 conflict
0x0d816e2e…67a1
0x34b655…2a6f
2 touches
0 conflicts
0x31734e80…921f
0x34b655…2a6f
2 touches
0 conflicts
0x37146d44…5b1b
0x34b655…2a6f
2 touches
0 conflicts
0x3b471477…d7c3
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 0xbd06525277…19c2c8
Audit this contract →
← previous block·next block →recent activity