← previous blocknext block →recent activity
Analyzing
Block #90,795,094
16 transactions · 16 stateful · 2026-07-27 14:26:06 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,795,094 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe069120c…952c
0x000000…012a
6 touches
3 conflicts
0xb0f4dbcb…926a
0x754704…b603
6 touches
3 conflicts
0x00000000…0005
0x465a0b…3980
6 touches
3 conflicts
0x99147084…f98d
0x465a0b…3980
6 touches
3 conflicts
0x2b8e1631…bed0
0x699abc…6a3b
6 touches
3 conflicts
0xa66e6a90…642f
0x699abc…6a3b
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
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