← previous blocknext block →recent activity
Analyzing
Block #90,918,909
22 transactions · 19 stateful · 2026-07-28 00:49:06 UTC
Parallelism
73/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,918,909 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w112w213w314w015w416w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x194876e0…27c6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x300c3654…ffc4
0x34b655…2a6f
6 touches
3 conflicts
0xe8249742…4c39
0x40c49f…2af0
4 touches
1 conflict
0x123ee74b…5510
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fb
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 0x4efae87285…886aa8
Audit this contract →
← previous block·next block →recent activity