← previous blocknext block →recent activity
Analyzing
Block #90,945,028
14 transactions · 14 stateful · 2026-07-28 03:00:29 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,945,028 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdc80bf7…e947
0x34b655…2a6f
10 touches
10 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5b1895ec…423a
0x34b655…2a6f
6 touches
3 conflicts
0x614f2962…6393
0x34b655…2a6f
6 touches
3 conflicts
0x9e04a514…7824
0x34b655…2a6f
4 touches
1 conflict
0xa6b48d6e…0705
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
10 conflicts on slot 0xbdc80bf733…aae947
Audit this contract →
← previous block·next block →recent activity