← previous blocknext block →recent activity
Analyzing
Block #102,216,063
50 transactions · 50 stateful · 2026-09-05 15:07:06 UTC
Parallelism
66/100
Blocked
62%
Avg conflicts / tx
3.26
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #102,216,063 · 50 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
1w02w13w04w17w28w314w115w422w524w634w736w837w938w1039w1140w1241w1343w1444w1545w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
32 touches
120 conflicts
0x482471ad…122f
0x34b655…2a6f
26 touches
78 conflicts
0x160cd79a…3468
0x34b655…2a6f
24 touches
66 conflicts
0x7e75b2f2…e147
0x34b655…2a6f
18 touches
36 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x256918f1…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
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
120 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity