← previous blocknext block →recent activity
Analyzing
Block #90,683,397
13 transactions · 11 stateful · 2026-07-27 05:04:11 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,683,397 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5a100ac0…96d3
0x34b655…2a6f
6 touches
3 conflicts
0xde61d0d0…b464
0x34b655…2a6f
4 touches
1 conflict
0x1ea36543…26ef
0x34b655…2a6f
4 touches
1 conflict
0x2cffc55c…f961
0x34b655…2a6f
4 touches
1 conflict
0x2fcd4130…b4a5
0xc8689a…ee79
4 touches
1 conflict
0x2130a548…c1de
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity