← previous blocknext block →recent activity
Analyzing
Block #90,649,957
24 transactions · 24 stateful · 2026-07-27 02:15:57 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,649,957 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w114w118w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00cb6e58…29c6
0x34b655…2a6f
8 touches
6 conflicts
0x58b580e4…cbf6
0x34b655…2a6f
8 touches
6 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x449d101e…ea3f
0xa6afd3…d132
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity