← previous blocknext block →recent activity
Analyzing
Block #90,978,061
20 transactions · 20 stateful · 2026-07-28 05:46:39 UTC
Parallelism
40/100
Blocked
60%
Avg conflicts / tx
3.4
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #90,978,061 · 20 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w17w28w39w410w511w612w713w814w915w1016w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x705ab4ae…0162
0x34b655…2a6f
20 touches
45 conflicts
0xbde524f4…43bf
0x34b655…2a6f
20 touches
45 conflicts
0x3ad8bbeb…b084
0x34b655…2a6f
10 touches
10 conflicts
0x840df1e4…bbfc
0x34b655…2a6f
7 touches
6 conflicts
0x33489b05…e6be
0x34b655…2a6f
5 touches
3 conflicts
0x737acb78…fce8
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
66 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity