← previous blocknext block →recent activity
Analyzing
Block #104,205,248
41 transactions · 36 stateful · 2026-09-12 14:38:10 UTC
Parallelism
83/100
Blocked
61%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,205,248 · 41 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
1w02w13w14w25w06w08w010w111w113w314w215w220w121w325w426w527w428w631w132w240w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d9f3717…44e7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5c8a8db2…8a6d
0x34b655…2a6f
8 touches
6 conflicts
0x0f43bfc7…1de5
0x34b655…2a6f
8 touches
6 conflicts
0x464a82ff…41de
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x9d9f371782…a844e7
Audit this contract →
← previous block·next block →recent activity