← previous blocknext block →recent activity
Analyzing
Block #91,040,393
7 transactions · 6 stateful · 2026-07-28 11:01:04 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,040,393 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x15551f94…1fbb
0x34b655…2a6f
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x48b58394…2894
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
2 touches
0 conflicts
0x694bf0dd…d36b
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x845ec8b071…13c1af
Audit this contract →
← previous block·next block →recent activity