← previous blocknext block →recent activity
Analyzing
Block #90,968,519
21 transactions · 17 stateful · 2026-07-28 04:58:39 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,968,519 · 21 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
7w08w19w210w311w412w416w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x83c48b61…dc9a
0x34b655…2a6f
6 touches
3 conflicts
0x43c2fa32…4d82
0x34b655…2a6f
6 touches
3 conflicts
0xf1345bef…5530
0x34b655…2a6f
6 touches
3 conflicts
0x46ae49d7…ce55
0x34b655…2a6f
4 touches
1 conflict
0x56e254bc…1215
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity