← previous blocknext block →recent activity
Analyzing
Block #90,856,050
15 transactions · 14 stateful · 2026-07-27 19:32:49 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,856,050 · 15 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
4w05w17w29w310w411w314w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x187bb168…d783
0x34b655…2a6f
4 touches
1 conflict
0x24e3bf88…17bf
0x34b655…2a6f
4 touches
1 conflict
0x2a38297c…67c8
0x34b655…2a6f
4 touches
1 conflict
0x33be4b45…d981
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x6634746e…884a
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 0x0d488000e2…143831
Audit this contract →
← previous block·next block →recent activity