← previous blocknext block →recent activity
Analyzing
Block #100,121,838
34 transactions · 30 stateful · 2026-08-29 07:13:45 UTC
Parallelism
59/100
Blocked
70%
Avg conflicts / tx
2.44
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #100,121,838 · 34 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w29w111w012w115w216w319w420w322w124w425w526w627w728w829w930w1031w1132w1233w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xbd590df7…9891
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x6f132c01…cdcc
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity