← previous blocknext block →recent activity
Analyzing
Block #92,346,133
9 transactions · 8 stateful · 2026-08-02 00:31:44 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,346,133 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bac238e…e5a1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa0f935db…1717
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf845b6ce…0547
0x34b655…2a6f
4 touches
1 conflict
0x425607a6…cd0c
0x34b655…2a6f
2 touches
0 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
2 touches
0 conflicts
0x5d7537fa…52ef
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 0x1bac238e39…8ee5a1
Audit this contract →
← previous block·next block →recent activity