← previous blocknext block →recent activity
Analyzing
Block #101,894,931
30 transactions · 29 stateful · 2026-09-04 11:59:01 UTC
Parallelism
43/100
Blocked
66%
Avg conflicts / tx
4.07
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #101,894,931 · 30 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w06w18w29w310w411w512w613w714w815w916w1023w324w1125w1226w1328w1529w16
- 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
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0x51cfbcbc…fa29
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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity