← previous blocknext block →recent activity
Analyzing
Block #90,240,289
14 transactions · 12 stateful · 2026-07-25 15:40:15 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,240,289 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xb69dd898…3e02
0x34b655…2a6f
6 touches
3 conflicts
0x73d31f9b…dd0b
0x34b655…2a6f
4 touches
1 conflict
0x7c1d804e…835c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7fa44fe8…484e
0x34b655…2a6f
4 touches
1 conflict
0x9d20b779…6b98
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity