← previous blocknext block →recent activity
Analyzing
Block #104,160,833
17 transactions · 17 stateful · 2026-09-12 10:52:43 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,160,833 · 17 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
1w02w13w25w36w48w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x8a294ae1…965c
0x34b655…2a6f
14 touches
21 conflicts
0x705a9a1a…db08
0x34b655…2a6f
12 touches
15 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0xecf541d2…4da9
0x34b655…2a6f
6 touches
3 conflicts
0xfc2493d3…6898
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity