← previous blocknext block →recent activity
Analyzing
Block #90,772,372
22 transactions · 20 stateful · 2026-07-27 12:31:45 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,772,372 · 22 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
4w05w16w08w09w110w211w112w314w416w218w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x454ea3b4…b25e
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x449d101e…ea3f
0xa6afd3…d132
6 touches
3 conflicts
0xd7badc5e…8c2b
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x15ae3bf3…2507
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 0x454ea3b4d6…89b25e
Audit this contract →
← previous block·next block →recent activity