← previous blocknext block →recent activity
Analyzing
Block #90,968,599
17 transactions · 17 stateful · 2026-07-28 04:59:03 UTC
Parallelism
35/100
Blocked
65%
Avg conflicts / tx
3.29
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #90,968,599 · 17 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w410w511w612w713w814w915w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0xce06a0f7…efef
0x34b655…2a6f
22 touches
55 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0xd021073a…271b
0x34b655…2a6f
9 touches
10 conflicts
0x5ca6ebb9…3142
0x34b655…2a6f
8 touches
6 conflicts
0x4030dc59…8a58
0x34b655…2a6f
7 touches
6 conflicts
0x81561f70…fefd
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
55 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity