← previous blocknext block →recent activity
Analyzing
Block #90,890,773
20 transactions · 16 stateful · 2026-07-27 22:27:33 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,890,773 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w07w19w010w211w314w116w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x0aa54240…f89e
0x34b655…2a6f
8 touches
6 conflicts
0xe03bbbf2…f240
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcffc17bc…3544
0x34b655…2a6f
6 touches
3 conflicts
0xb5681617…e980
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 0xcdc1731c6b…b6b91a
Audit this contract →
← previous block·next block →recent activity