← previous blocknext block →recent activity
Analyzing
Block #91,090,054
18 transactions · 16 stateful · 2026-07-28 15:10:58 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,090,054 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xea0cb631…c37b
0x34b655…2a6f
6 touches
3 conflicts
0xdd50db55…0ace
0x34b655…2a6f
6 touches
3 conflicts
0x8a67a382…57f7
0x34b655…2a6f
5 touches
3 conflicts
0x20492d53…80f9
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity