← previous blocknext block →recent activity
Analyzing
Block #90,881,199
14 transactions · 13 stateful · 2026-07-27 21:39:23 UTC
Parallelism
43/100
Blocked
62%
Avg conflicts / tx
1.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,881,199 · 14 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
1w02w13w25w36w49w510w612w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26d1c221…4d2a
0x34b655…2a6f
10 touches
10 conflicts
0x1eac6e74…32cd
0x34b655…2a6f
10 touches
10 conflicts
0xecdfdfa3…619b
0x34b655…2a6f
6 touches
3 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xa8699068…3031
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
10 conflicts on slot 0x26d1c221d7…ef4d2a
Audit this contract →
← previous block·next block →recent activity