← previous blocknext block →recent activity
Analyzing
Block #90,288,846
9 transactions · 9 stateful · 2026-07-25 19:45:35 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,288,846 · 9 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
2w03w14w25w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1d6a4ee3…b056
0x34b655…2a6f
4 touches
1 conflict
0x1febc2d0…0136
0x34b655…2a6f
4 touches
1 conflict
0x237fbe48…657b
0x34b655…2a6f
4 touches
1 conflict
0x3cd30154…5939
0x34b655…2a6f
4 touches
1 conflict
0x4d73f502…968b
0x34b655…2a6f
4 touches
1 conflict
0x5db9be70…5fe1
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity