← previous blocknext block →recent activity
Analyzing
Block #90,787,015
25 transactions · 22 stateful · 2026-07-27 13:45:25 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,787,015 · 25 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
1w03w16w07w18w29w310w411w512w615w519w220w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xc755c95b…6814
0x34b655…2a6f
6 touches
3 conflicts
0x5e8223c2…c242
0x34b655…2a6f
6 touches
3 conflicts
0x272e5bd6…252d
0x34b655…2a6f
4 touches
1 conflict
0x281e160c…fdf2
0x34b655…2a6f
4 touches
1 conflict
0x2f358e74…1022
0x34b655…2a6f
4 touches
1 conflict
0x4269c153…365a
0x34b655…2a6f
4 touches
1 conflict
0x4ae3b148…7ed2
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity