← previous blocknext block →recent activity
Analyzing
Block #90,818,556
12 transactions · 12 stateful · 2026-07-27 16:24:14 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,818,556 · 12 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
2w07w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2a49f3bf…713b
0x34b655…2a6f
4 touches
1 conflict
0x0c233c18…37bb
0x34b655…2a6f
2 touches
0 conflicts
0x0c233c18…37bc
0x34b655…2a6f
2 touches
0 conflicts
0x0fbeb37e…1b04
0x34b655…2a6f
2 touches
0 conflicts
0x102ce31f…1e8b
0x34b655…2a6f
2 touches
0 conflicts
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity