← previous blocknext block →recent activity
Analyzing
Block #104,847,339
38 transactions · 32 stateful · 2026-09-14 20:53:11 UTC
Parallelism
82/100
Blocked
34%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,847,339 · 38 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
1w02w13w14w05w111w012w113w214w315w416w522w623w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb856d1a1…1f18
0x34b655…2a6f
14 touches
21 conflicts
0x424e9119…2032
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xfe2577ac…677b
0x34b655…2a6f
12 touches
15 conflicts
0x8b96c207…5675
0x34b655…2a6f
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x1f06ee2d…7f6d
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 0xb856d1a127…bf1f18
Audit this contract →
← previous block·next block →recent activity