← previous blocknext block →recent activity
Analyzing
Block #90,213,414
14 transactions · 12 stateful · 2026-07-25 13:24:44 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,213,414 · 14 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
6w07w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe8237d0…29e4
0x34b655…2a6f
4 touches
1 conflict
0xccb8c4ac…aa07
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd9a771df…a27b
0x34b655…2a6f
4 touches
1 conflict
0xe305dec6…cf69
0x34b655…2a6f
4 touches
1 conflict
0xe5f9a967…ee64
0x34b655…2a6f
4 touches
1 conflict
0x1038d144…6054
0x34b655…2a6f
4 touches
1 conflict
0x1d6ce97a…901b
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
1 conflict on slot 0xfe8237d0b6…3929e4
Audit this contract →
← previous block·next block →recent activity