← previous blocknext block →recent activity
Analyzing
Block #92,161,797
11 transactions · 11 stateful · 2026-08-01 09:04:41 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,161,797 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc6352168…e091
0x34b655…2a6f
4 touches
1 conflict
0x2b209d22…89d1
0x065c9d…c394
2 touches
0 conflicts
0x76dce3f2…8387
0x065c9d…c394
2 touches
0 conflicts
0x9dbf410c…861e
0x065c9d…c394
2 touches
0 conflicts
0xade4ab85…be36
0x065c9d…c394
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity