← previous blocknext block →recent activity
Analyzing
Block #104,876,899
56 transactions · 52 stateful · 2026-09-14 23:22:00 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
2.73
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #104,876,899 · 56 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w010w112w214w315w419w120w124w325w426w527w628w729w830w941w1043w1144w146w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x8af736e2…714f
0x34b655…2a6f
10 touches
10 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x54919cee…dd00
0x34b655…2a6f
9 touches
10 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
78 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity