← previous blocknext block →recent activity
Analyzing
Block #90,785,324
19 transactions · 18 stateful · 2026-07-27 13:36:55 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,785,324 · 19 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
2w03w14w07w19w110w211w312w413w514w616w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x4bc1abab…5874
0x34b655…2a6f
10 touches
10 conflicts
0xf0d54a25…4cc8
0x34b655…2a6f
6 touches
3 conflicts
0xfd631a49…bec9
0x34b655…2a6f
5 touches
3 conflicts
0x5abb42a7…8507
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity