← previous blocknext block →recent activity
Analyzing
Block #90,994,392
24 transactions · 23 stateful · 2026-07-28 07:09:00 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,994,392 · 24 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
1w02w13w26w08w09w010w111w312w216w017w118w219w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff3d6184…43dd
0x34b655…2a6f
6 touches
3 conflicts
0x421099c9…8896
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x120847e2…98c2
0x34b655…2a6f
4 touches
1 conflict
0x1a9f678f…302a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xff3d6184d8…b143dd
Audit this contract →
← previous block·next block →recent activity