← previous blocknext block →recent activity
Analyzing
Block #92,588,262
11 transactions · 11 stateful · 2026-08-02 20:49:28 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,588,262 · 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
2w03w14w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4cd050f…fafc
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa8b8fbde…396d
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
3 conflicts on slot 0xe4cd050f63…53fafc
Audit this contract →
← previous block·next block →recent activity