← previous blocknext block →recent activity
Analyzing
Block #90,213,041
15 transactions · 15 stateful · 2026-07-25 13:22:51 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,213,041 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w59w610w711w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
16 touches
28 conflicts
0x55b4e430…44cb
0x754704…b603
16 touches
28 conflicts
0x082c0739…fe64
0x0a2fbf…29b1
16 touches
28 conflicts
0x082c0739…fe65
0x0a2fbf…29b1
16 touches
28 conflicts
0x0a68df54…db93
0x0a2fbf…29b1
16 touches
28 conflicts
0x0a68df54…db94
0x0a2fbf…29b1
16 touches
28 conflicts
0x0a68df54…db97
0x0a2fbf…29b1
16 touches
28 conflicts
0x00000000…0006
0x0a2fbf…29b1
16 touches
28 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: 0x370e2ee6…bd63b4
28 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity