← previous blocknext block →recent activity
Analyzing
Block #90,439,880
13 transactions · 13 stateful · 2026-07-26 08:38:46 UTC
Parallelism
46/100
Blocked
46%
Avg conflicts / tx
1.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,439,880 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8905db2e…630c
0x34b655…2a6f
12 touches
15 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
8 touches
6 conflicts
0x96c6ca66…371b
0x34b655…2a6f
8 touches
6 conflicts
0xf17c63a1…a36b
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
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
21 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity