← previous blocknext block →recent activity
Analyzing
Block #102,643,684
34 transactions · 32 stateful · 2026-09-07 03:13:29 UTC
Parallelism
50/100
Blocked
75%
Avg conflicts / tx
4.06
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #102,643,684 · 34 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
1w02w13w24w35w47w19w312w517w619w622w723w825w826w927w1028w1129w1230w1331w1432w1533w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
18 touches
36 conflicts
0x7dd96c96…7335
0x34b655…2a6f
18 touches
36 conflicts
0x22f10271…841d
0x34b655…2a6f
14 touches
21 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
12 touches
15 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
12 touches
15 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity