← previous blocknext block →recent activity
Analyzing
Block #90,322,878
24 transactions · 24 stateful · 2026-07-25 22:38:38 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,322,878 · 24 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
1w05w17w08w19w014w117w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0xf1756174…a034
0x34b655…2a6f
6 touches
3 conflicts
0xbc89da14…a1b5
0x34b655…2a6f
6 touches
3 conflicts
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x7175a904…640c
0x34b655…2a6f
4 touches
1 conflict
0x751ef542…90d8
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity