← previous blocknext block →recent activity
Analyzing
Block #105,843,705
18 transactions · 15 stateful · 2026-09-18 08:29:22 UTC
Parallelism
39/100
Blocked
67%
Avg conflicts / tx
1.67
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,843,705 · 18 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
1w02w18w29w310w411w512w613w714w815w916w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x198a4172…bc4f
0x34b655…2a6f
14 touches
21 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
14 touches
21 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x7dafda9c…6c6a
0x34b655…2a6f
10 touches
10 conflicts
0xff7cb355…3404
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
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
21 conflicts on slot 0x198a417284…89bc4f
Audit this contract →
← previous block·next block →recent activity