← previous blocknext block →recent activity
Analyzing
Block #90,213,023
14 transactions · 11 stateful · 2026-07-25 13:22:45 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,213,023 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4faee57c…6ca2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfaf3835b…98c7
0x34b655…2a6f
4 touches
1 conflict
0x3e3b859f…3654
0x34b655…2a6f
4 touches
1 conflict
0x531db7af…9f89
0x34b655…2a6f
4 touches
1 conflict
0x5b2d25ba…eb48
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
3 conflicts on slot 0x4faee57c94…686ca2
Audit this contract →
← previous block·next block →recent activity