← previous blocknext block →recent activity
Analyzing
Block #90,540,108
11 transactions · 10 stateful · 2026-07-26 17:03:20 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,540,108 · 11 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
1w02w14w06w17w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfefce52e…6ad5
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0xabd0bcfc…64e2
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
1 conflict on slot 0xfefce52e10…c56ad5
Audit this contract →
← previous block·next block →recent activity