← previous blocknext block →recent activity
Analyzing
Block #90,455,136
7 transactions · 7 stateful · 2026-07-26 09:55:52 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,455,136 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x025fef2f…9738
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x08803a9b…dfbd
0x34b655…2a6f
2 touches
0 conflicts
0x08b68583…01a1
0x34b655…2a6f
2 touches
0 conflicts
0x1f898cb9…9692
0x34b655…2a6f
2 touches
0 conflicts
0x33be4b45…d981
0x34b655…2a6f
2 touches
0 conflicts
0x3b552ea8…3a4b
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x025fef2fae…b69738
Audit this contract →
← previous block·next block →recent activity