← previous blocknext block →recent activity
Analyzing
Block #91,424,623
53 transactions · 41 stateful · 2026-07-29 19:16:10 UTC
Parallelism
66/100
Blocked
66%
Avg conflicts / tx
2.43
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #91,424,623 · 53 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w18w210w211w312w413w515w620w721w831w135w1036w1137w1239w1440w1541w1642w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
10 touches
10 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004b
0x80c745…7210
10 touches
10 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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity