← previous blocknext block →recent activity
Analyzing
Block #90,629,955
10 transactions · 8 stateful · 2026-07-27 00:35:19 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,629,955 · 10 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
2w03w14w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc3d5171…8357
0x34b655…2a6f
6 touches
3 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x502b445c…c1e5
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0xf9ac650a…d82d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xfc3d51716d…008357
Audit this contract →
← previous block·next block →recent activity