← previous blocknext block →recent activity
Analyzing
Block #90,648,984
17 transactions · 17 stateful · 2026-07-27 02:11:03 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,648,984 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w07w110w211w114w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb05cd4f5…73d0
0x2b46c0…1669
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x449d101e…ea3f
0xa6afd3…d132
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0xd7badc5e…8c2b
0xa6afd3…d132
6 touches
3 conflicts
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: 0x2b46c08c…ec1669
3 conflicts on slot 0xb05cd4f5f9…f973d0
Audit this contract →
← previous block·next block →recent activity