← previous blocknext block →recent activity
Analyzing
Block #90,026,737
16 transactions · 13 stateful · 2026-07-24 21:40:57 UTC
Parallelism
63/100
Blocked
62%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,026,737 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w16w27w38w412w414w215w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3727225e…a3cf
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x4fb86cd0…c67b
0x34b655…2a6f
6 touches
3 conflicts
0x6269fda0…5714
0x34b655…2a6f
6 touches
3 conflicts
0x6b47245e…a342
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0x310c9baa…ec0b
0x34b655…2a6f
6 touches
3 conflicts
0xbba0744d…9d58
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x3727225e82…15a3cf
Audit this contract →
← previous block·next block →recent activity