← previous blocknext block →recent activity
Analyzing
Block #104,192,592
20 transactions · 18 stateful · 2026-09-12 13:33:44 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,192,592 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w09w210w311w313w414w515w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91f679af…6ac5
0x34b655…2a6f
12 touches
15 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6507044e…bcd6
0x34b655…2a6f
8 touches
6 conflicts
0x9ddfd674…2a54
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0x91f679af07…936ac5
Audit this contract →
← previous block·next block →recent activity