← previous blocknext block →recent activity
Analyzing
Block #103,987,128
19 transactions · 19 stateful · 2026-09-11 20:09:00 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #103,987,128 · 19 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w511w612w715w818w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dedaff6…161b
0x34b655…2a6f
16 touches
28 conflicts
0x0942947e…563a
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0x9ec9f52c…cf48
0x34b655…2a6f
16 touches
28 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
16 touches
28 conflicts
0x9a8af3c2…e4ae
0x34b655…2a6f
16 touches
28 conflicts
0xbb455bd6…adc7
0x34b655…2a6f
15 touches
28 conflicts
0xab161cd0…c92d
0x34b655…2a6f
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
28 conflicts on slot 0x6dedaff684…2d161b
Audit this contract →
← previous block·next block →recent activity