← previous blocknext block →recent activity
Analyzing
Block #90,530,771
18 transactions · 14 stateful · 2026-07-26 16:16:22 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,530,771 · 18 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
4w05w06w17w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc96083d…124d
0x34b655…2a6f
6 touches
3 conflicts
0xca1e97f0…b24a
0x34b655…2a6f
4 touches
1 conflict
0x7f7b37e3…c534
0x34b655…2a6f
4 touches
1 conflict
0x85d9196c…04e3
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca1e97f0…b249
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 0xbc96083d67…f4124d
Audit this contract →
← previous block·next block →recent activity