← previous blocknext block →recent activity
Analyzing
Block #90,697,479
19 transactions · 18 stateful · 2026-07-27 06:15:01 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,697,479 · 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
2w03w14w25w37w48w510w011w312w113w414w517w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa505051b…0632
0x34b655…2a6f
6 touches
3 conflicts
0x53d6f1c9…16c4
0x34b655…2a6f
4 touches
1 conflict
0x6b276a77…8c6e
0x34b655…2a6f
4 touches
1 conflict
0x6d85c11e…9c54
0x34b655…2a6f
4 touches
1 conflict
0x85c84f98…06d7
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity