← previous blocknext block →recent activity
Analyzing
Block #102,560,853
20 transactions · 20 stateful · 2026-09-06 20:14:24 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,560,853 · 20 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
1w02w13w24w05w16w27w311w113w014w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38aa1898…fdf5
0xd3bbba…1901
8 touches
6 conflicts
0x71c367a9…3c16
0x188d58…ea8e
8 touches
6 conflicts
0x1342557a…df31
0x27bc99…9a93
8 touches
6 conflicts
0x848aa2c3…3e8d
0x27bc99…9a93
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x17359e55…7914
0x188d58…ea8e
8 touches
6 conflicts
0x84611dd3…b347
0x1b6862…e19c
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: 0xd3bbbae9…6a1901
6 conflicts on slot 0x38aa189812…48fdf5
Audit this contract →
← previous block·next block →recent activity