← previous blocknext block →recent activity
Analyzing
Block #104,160,793
21 transactions · 20 stateful · 2026-09-12 10:52:31 UTC
Parallelism
48/100
Blocked
60%
Avg conflicts / tx
2.62
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #104,160,793 · 21 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
1w02w13w04w15w26w37w18w49w510w613w716w817w919w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1408e7c7…f324
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x95f13179…a528
0x34b655…2a6f
12 touches
15 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
7 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x08cc68a2…2a59
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
45 conflicts on slot 0x1408e7c773…87f324
Audit this contract →
← previous block·next block →recent activity