← previous blocknext block →recent activity
Analyzing
Block #90,226,476
7 transactions · 6 stateful · 2026-07-25 14:30:36 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,226,476 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b6c252d…a696
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7c36395e…ac80
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x1dead3d3…fdc4
0x34b655…2a6f
2 touches
0 conflicts
0x1ebb35bb…ef2a
0x34b655…2a6f
2 touches
0 conflicts
0x226e3b61…5e6f
0x34b655…2a6f
2 touches
0 conflicts
0x24e3bf88…17bf
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 0x7b6c252d22…b1a696
Audit this contract →
← previous block·next block →recent activity