← previous blocknext block →recent activity
Analyzing
Block #104,199,045
26 transactions · 25 stateful · 2026-09-12 14:06:36 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1.92
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #104,199,045 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w26w37w110w419w820w121w222w923w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b621a7d…2611
0x34b655…2a6f
14 touches
21 conflicts
0x4ccfe55c…de03
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641e
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xfd401f8a…aae5
0xa6afd3…d132
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
21 conflicts on slot 0x0b621a7ddd…e82611
Audit this contract →
← previous block·next block →recent activity