← previous blocknext block →recent activity
Analyzing
Block #102,053,813
42 transactions · 39 stateful · 2026-09-05 01:24:32 UTC
Parallelism
76/100
Blocked
72%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,053,813 · 42 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w410w515w326w327w429w531w635w536w737w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc852b267…9d14
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xcef187be…1857
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd1480c90…ae07
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xc852b26715…339d14
Audit this contract →
← previous block·next block →recent activity