← previous blocknext block →recent activity
Analyzing
Block #90,960,107
33 transactions · 32 stateful · 2026-07-28 04:16:19 UTC
Parallelism
51/100
Blocked
66%
Avg conflicts / tx
3.33
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #90,960,107 · 33 txs across 16 waves · depth 16
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
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w09w111w214w316w417w518w619w720w821w922w1023w1124w1225w1326w1427w1529w330w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
28 touches
91 conflicts
0xce06a0f7…efef
0x34b655…2a6f
24 touches
66 conflicts
0xbde524f4…43bf
0x34b655…2a6f
24 touches
66 conflicts
0x81561f70…fefd
0x34b655…2a6f
22 touches
55 conflicts
0x4030dc59…8a58
0x34b655…2a6f
11 touches
15 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
10 touches
10 conflicts
0x97915d13…24b9
0x34b655…2a6f
9 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 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
91 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity