← previous blocknext block →recent activity
Analyzing
Block #90,889,057
16 transactions · 16 stateful · 2026-07-27 22:18:55 UTC
Parallelism
44/100
Blocked
63%
Avg conflicts / tx
2.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #90,889,057 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w69w710w812w115w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x2bbc37af…2efe
0x34b655…2a6f
4 touches
1 conflict
0x2d41d6d2…71d0
0x34b655…2a6f
4 touches
1 conflict
0x427b538b…124f
0x34b655…2a6f
4 touches
1 conflict
0x4a14ad81…5301
0x34b655…2a6f
4 touches
1 conflict
0x4b76f967…295f
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity