← previous blocknext block →recent activity
Analyzing
Block #92,111,373
13 transactions · 12 stateful · 2026-08-01 04:51:03 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,111,373 · 13 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
2w04w06w17w29w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ba216b2…eec2
0x34b655…2a6f
4 touches
1 conflict
0x1a843f41…02aa
0x34b655…2a6f
4 touches
1 conflict
0x13d41051…824c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
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
1 conflict on slot 0x7ba216b264…52eec2
Audit this contract →
← previous block·next block →recent activity