← previous blocknext block →recent activity
Analyzing
Block #101,668,755
31 transactions · 29 stateful · 2026-09-03 17:01:11 UTC
Parallelism
42/100
Blocked
72%
Avg conflicts / tx
4.35
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #101,668,755 · 31 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
1w02w03w04w15w26w17w08w114w115w316w419w620w723w1024w1125w1226w1327w1429w1630w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0xb409e204…89ac
0x34b655…2a6f
14 touches
21 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
8 touches
6 conflicts
0x537e2e5b…c3ab
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x4089d428…b018
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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity