← previous blocknext block →recent activity
Analyzing
Block #90,886,653
19 transactions · 18 stateful · 2026-07-27 22:06:49 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,886,653 · 19 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
1w02w13w14w25w06w17w28w110w313w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe54b7d5…1bda
0x34b655…2a6f
6 touches
3 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x513ff642…18e3
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
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
3 conflicts on slot 0xbe54b7d5c9…2a1bda
Audit this contract →
← previous block·next block →recent activity