← previous blocknext block →recent activity
Analyzing
Block #90,437,426
10 transactions · 10 stateful · 2026-07-26 08:26:14 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,437,426 · 10 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
3w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2b37cdc…e470
0x34b655…2a6f
4 touches
1 conflict
0x0a906ba5…2454
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x08b68583…01a1
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6a
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6b
0x34b655…2a6f
2 touches
0 conflicts
0x36b256e4…f66a
0x34b655…2a6f
2 touches
0 conflicts
0x442bf747…dbdf
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 0xc2b37cdc32…c4e470
Audit this contract →
← previous block·next block →recent activity