← previous blocknext block →recent activity
Analyzing
Block #93,266,577
16 transactions · 15 stateful · 2026-08-05 05:44:00 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,266,577 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w26w310w011w412w513w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24933e74…db08
0x34b655…2a6f
12 touches
15 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0x55ce57a3…f7d1
0x34b655…2a6f
4 touches
1 conflict
0x43e15ca4…039d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
15 conflicts on slot 0x24933e7400…28db08
Audit this contract →
← previous block·next block →recent activity