← previous blocknext block →recent activity
Analyzing
Block #90,292,238
19 transactions · 18 stateful · 2026-07-25 20:02:49 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,292,238 · 19 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
1w02w18w29w010w011w114w215w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17fa2c17…5797
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x231ebd56…a3b7
0xd32edf…ff58
5 touches
3 conflicts
0x90d127f4…5c92
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x390dd46c…deef
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 0x17fa2c17e7…e25797
Audit this contract →
← previous block·next block →recent activity