← previous blocknext block →recent activity
Analyzing
Block #90,211,492
18 transactions · 15 stateful · 2026-07-25 13:15:03 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,211,492 · 18 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
3w04w17w18w29w310w415w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x749a4cb2…15f8
0x34b655…2a6f
4 touches
1 conflict
0x77704719…12d9
0x34b655…2a6f
4 touches
1 conflict
0x8817ea9b…8b07
0x34b655…2a6f
4 touches
1 conflict
0x8c7eac39…f34d
0x34b655…2a6f
4 touches
1 conflict
0x8d3e8f8c…8de4
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity