← previous blocknext block →recent activity
Analyzing
Block #92,805,268
19 transactions · 19 stateful · 2026-08-03 15:02:13 UTC
Parallelism
63/100
Blocked
37%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,805,268 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf9150155…e080
0x34b655…2a6f
4 touches
1 conflict
0x0c21cc22…f749
0x34b655…2a6f
4 touches
1 conflict
0x4b570446…c4c1
0x34b655…2a6f
4 touches
1 conflict
0x95e66f95…e987
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity