← previous blocknext block →recent activity
Analyzing
Block #90,213,448
17 transactions · 13 stateful · 2026-07-25 13:24:54 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,213,448 · 17 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
2w03w16w27w39w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0a1643e3…e20d
0x34b655…2a6f
4 touches
1 conflict
0x1741dbc0…73a7
0x34b655…2a6f
4 touches
1 conflict
0x58d6b9cf…7c9e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x749a4cb2…15f8
0x34b655…2a6f
4 touches
1 conflict
0x823a3658…acf6
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 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity