← previous blocknext block →recent activity
Analyzing
Block #102,043,161
51 transactions · 43 stateful · 2026-09-05 00:30:32 UTC
Parallelism
80/100
Blocked
70%
Avg conflicts / tx
2.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,043,161 · 51 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
1w02w13w24w36w29w410w511w614w117w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xf3d10975…0d07
0x34b655…2a6f
16 touches
28 conflicts
0xfa7ea729…e62e
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
12 touches
15 conflicts
0x839c0c71…bada
0x34b655…2a6f
12 touches
15 conflicts
0x77ed432f…fa04
0x065c9d…c394
12 touches
15 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
36 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity