← previous blocknext block →recent activity
Analyzing
Block #90,374,708
18 transactions · 17 stateful · 2026-07-26 03:03:48 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,374,708 · 18 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
4w05w18w09w110w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x623f9de0…aec2
0x0a2fbf…29b1
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x623f9de0…aebe
0x0a2fbf…29b1
6 touches
3 conflicts
0x623f9de0…aebf
0x0a2fbf…29b1
6 touches
3 conflicts
0x30e3f228…0d43
0x34b655…2a6f
4 touches
1 conflict
0x54836d65…80ab
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x623f9de031…83aec2
Audit this contract →
← previous block·next block →recent activity