← previous blocknext block →recent activity
Analyzing
Block #90,820,851
19 transactions · 18 stateful · 2026-07-27 16:35:46 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,820,851 · 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
2w03w04w05w16w17w28w110w013w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x24eaf46d…8c2e
0x34b655…2a6f
8 touches
6 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
6 touches
3 conflicts
0xba46b844…c049
0x34b655…2a6f
4 touches
1 conflict
0x449d101e…ea3f
0xa6afd3…d132
4 touches
1 conflict
0x40388e0a…9f5d
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
10 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity