← previous blocknext block →recent activity
Analyzing
Block #92,358,524
16 transactions · 16 stateful · 2026-08-02 01:34:03 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,358,524 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w211w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
8 touches
6 conflicts
0x4c22021d…f8a7
0x34b655…2a6f
6 touches
3 conflicts
0xebd735e5…ea5d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0xe40ce249…a28c
0x34b655…2a6f
6 touches
3 conflicts
0x0b34a794…400b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity