← previous blocknext block →recent activity
Analyzing
Block #90,946,713
15 transactions · 14 stateful · 2026-07-28 03:08:57 UTC
Parallelism
40/100
Blocked
57%
Avg conflicts / tx
2.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #90,946,713 · 15 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w38w49w511w612w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
8 touches
6 conflicts
0x064a19b6…3f1d
0x34b655…2a6f
8 touches
6 conflicts
0xbdc80bf7…e947
0x34b655…2a6f
6 touches
3 conflicts
0xd7668c61…55f8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity