← previous blocknext block →recent activity
Analyzing
Block #104,166,970
20 transactions · 19 stateful · 2026-09-12 11:23:52 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,166,970 · 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
1w02w13w14w27w112w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaeefeb3…889f
0x34b655…2a6f
16 touches
28 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xa3250389…8774
0x34b655…2a6f
8 touches
6 conflicts
0x1a69c7c5…09cc
0x34b655…2a6f
6 touches
3 conflicts
0x0aa5e418…5d1d
0x34b655…2a6f
6 touches
3 conflicts
0x9a6bc012…7495
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
28 conflicts on slot 0xfaeefeb349…b8889f
Audit this contract →
← previous block·next block →recent activity