← previous blocknext block →recent activity
Analyzing
Block #90,689,686
10 transactions · 9 stateful · 2026-07-27 05:35:49 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,689,686 · 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
1w02w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51861f55…065b
0x34b655…2a6f
2 touches
0 conflicts
0x5d3bdba3…669e
0x34b655…2a6f
2 touches
0 conflicts
0x6a9f6919…4b74
0x34b655…2a6f
2 touches
0 conflicts
0x70cfbacf…5c46
0x34b655…2a6f
2 touches
0 conflicts
0x72083f0d…082a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity