← previous blocknext block →recent activity
Analyzing
Block #90,515,015
18 transactions · 17 stateful · 2026-07-26 14:57:07 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,515,015 · 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
1w02w14w05w17w18w212w013w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xffa253d9…9333
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x24ca1902…7a87
0x34b655…2a6f
4 touches
1 conflict
0x3ab86b5a…8290
0x34b655…2a6f
4 touches
1 conflict
0x43076802…d920
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
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 0xc824469a90…af6426
Audit this contract →
← previous block·next block →recent activity