← previous blocknext block →recent activity
Analyzing
Block #90,816,931
23 transactions · 21 stateful · 2026-07-27 16:16:03 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,816,931 · 23 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
1w02w13w26w07w18w29w010w111w216w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x44ed742f…63f5
0x3bd359…433a
6 touches
3 conflicts
0x4eb758b8…b13b
0x3bd359…433a
6 touches
3 conflicts
0xc9d85869…8531
0x3bd359…433a
6 touches
3 conflicts
0xf45a6126…89bf
0x436662…7777
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x00000000…0004
0x510e44…2cd9
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity