← previous blocknext block →recent activity
Analyzing
Block #104,194,542
22 transactions · 19 stateful · 2026-09-12 13:43:42 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,194,542 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w112w213w315w416w517w618w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bd00bf7…752d
0x34b655…2a6f
14 touches
21 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb5924647…4cf1
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xa527a5f0…89ca
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 0x8bd00bf773…33752d
Audit this contract →
← previous block·next block →recent activity