← previous blocknext block →recent activity
Analyzing
Block #90,629,034
8 transactions · 6 stateful · 2026-07-27 00:30:41 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,629,034 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fd0b86c…b37c
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x1062ca99…dc10
0x34b655…2a6f
4 touches
1 conflict
0x30d58b0b…8806
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x24f8bfb5…8acb
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 0x6fd0b86c31…77b37c
Audit this contract →
← previous block·next block →recent activity