← previous blocknext block →recent activity
Analyzing
Block #91,439,382
27 transactions · 26 stateful · 2026-07-29 20:30:39 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,439,382 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w28w312w414w515w616w117w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x08a39015…efa0
0x34b655…2a6f
8 touches
6 conflicts
0xb6334806…c949
0x34b655…2a6f
8 touches
6 conflicts
0xe7b194de…c0f3
0x34b655…2a6f
6 touches
3 conflicts
0x71c72ebc…dbbb
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity