← previous blocknext block →recent activity
Analyzing
Block #90,797,183
21 transactions · 17 stateful · 2026-07-27 14:36:36 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,797,183 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w09w112w015w116w117w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd6941a1…6281
0x34b655…2a6f
6 touches
3 conflicts
0x45ef9175…5ab2
0x34b655…2a6f
4 touches
1 conflict
0xd253247a…5d1f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xbd6941a1b1…836281
Audit this contract →
← previous block·next block →recent activity