← previous blocknext block →recent activity
Analyzing
Block #90,947,328
14 transactions · 14 stateful · 2026-07-28 03:12:03 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,947,328 · 14 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
2w04w05w16w07w19w210w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ab4c88c…49f2
0x34b655…2a6f
6 touches
3 conflicts
0x723b37b4…facd
0x34b655…2a6f
6 touches
3 conflicts
0x7da6eb60…b34e
0x34b655…2a6f
6 touches
3 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
6 touches
3 conflicts
0xdc8ace40…4daf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbdc80bf7…e947
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 0x1ab4c88c84…1d49f2
Audit this contract →
← previous block·next block →recent activity