← previous blocknext block →recent activity
Analyzing
Block #102,383,059
35 transactions · 29 stateful · 2026-09-06 05:13:13 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,383,059 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w010w011w113w124w025w126w228w129w132w033w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f10271…841d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x422d5490…52d9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x604ef84a…7be1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x3293a887…43ff
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0x22f10271ce…96841d
Audit this contract →
← previous block·next block →recent activity