← previous blocknext block →recent activity
Analyzing
Block #90,686,869
18 transactions · 15 stateful · 2026-07-27 05:21:39 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,686,869 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w09w010w112w114w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62dbeb4d…a388
0x34b655…2a6f
6 touches
3 conflicts
0xde945aa8…1ad5
0xa6afd3…d132
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x6c6dcf34…6eb6
0x34b655…2a6f
4 touches
1 conflict
0x6f6b4878…d72d
0x34b655…2a6f
4 touches
1 conflict
0x9fc4538b…b4e9
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xbedefe84…fc7b
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 0x62dbeb4d5d…05a388
Audit this contract →
← previous block·next block →recent activity