← previous blocknext block →recent activity
Analyzing
Block #92,175,895
14 transactions · 14 stateful · 2026-08-01 10:15:35 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,175,895 · 14 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
1w02w13w25w37w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x260ca8fe…895a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc0bee456…40e9
0x34b655…2a6f
4 touches
1 conflict
0xa538ac07…fc9f
0x34b655…2a6f
4 touches
1 conflict
0xa538ac07…fc9e
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
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 0x260ca8fe2b…44895a
Audit this contract →
← previous block·next block →recent activity